The box

In developmentThis is being built and is not available yet. See what is available now.

A box is an isolated machine that runs on TNTHUB’s compute. It comes up with an SSH server already running. You connect to it and you run whatever you want — there is no runtime layer, no agent lifecycle manager, no opinion about what the box is for.

The reason it exists is a small, concrete annoyance: an agent that stops when your laptop sleeps. If you close the lid on a machine running your agent, the agent stops with it. Put the agent in a box instead and the box does not care whether your laptop is open.

Why it is not just a shell

A shell is not the product. The product is the combination of three things that are annoying to do yourself:

  • It stays up. The box keeps running whether or not you are connected to it. Disconnecting does not end the work, and it does not kill the process you left running.
  • It is disposable. A box is created for a piece of work and destroyed when you are finished with it. Nothing you leave behind is inherited by the next person or the next tenant.
  • It is reachable without exposing anything. You reach it through the platform, not by opening a port on the internet. There is no key file to copy around and no inbound firewall rule to get wrong.

Getting in

Everything happens through the tnt command. The platform API is on the same domain as this documentation, so there is nothing else to install or point at.

# Create a box
tnt box create --name research

# See what you have
tnt box list

# Open a shell in it
tnt box ssh-proxy ssh research

# Run one command and come back
tnt box exec research -- npm test

# Throw it away
tnt box destroy research

tnt box ssh-proxy ssh is the important one. It starts a local proxy that carries the SSH connection to the box, and then hands you an ordinary SSH session — so your editor, your terminal multiplexer, scp, and your ~/.ssh/config all work exactly as they do against any other machine. You are not learning a new remote shell; you are getting a shell somewhere else.

The proxy also means the box never needs an inbound port on the public internet. The connection is initiated from your side, every time.

What you can run in it

Anything. That is the point.

The useful cases tend to be one of these:

An agent that has to keep working. Start your coding agent in the box, let it work through a long task, and close your laptop. Come back later and read the log.

tnt box ssh-proxy ssh research
# then, on the box
opencode serve --port 4096

A long build. Test suites that take forty minutes do not have to survive a dropped connection.

A service you want to point something at. A staging API, a fixture server, a database with the exact version you need.

A throwaway environment for something risky. A package that might not behave, a script from a stranger, a reproduction you do not want on your laptop.

Lifecycle

A box moves through a small number of states.

StateWhat it means
creatingThe machine is being provisioned. Nothing is running yet.
runningIt is up. The SSH server is accepting connections.
idleIt is running but has not been touched for a while. It can still be reached.
reclaimedThe idle window passed, so it was destroyed.
destroyedYou asked for it to go, and it did.

Idle reclamation. A box that nobody touches for the idle window is torn down automatically, and its contents are destroyed with it. This is not a limit we invented to make the numbers work; it is the only way to keep a fleet of machines from accumulating. We will state the window here, in the open, before the box ships.

Snapshots. A reclaimed box can be re-provisioned from the snapshot it was taken at, which is fast, because the snapshot and the machine image are immutable. You get a fresh box with the same contents and a clean slate.

Destruction is final. A destroyed box is gone. There is no undo, and there is no recycle bin. Anything you want to keep, you take out first.

Where it runs, and what that means

Boxes run on TNTHUB’s compute. That is a deliberate part of the design, and it is worth being precise about what it means.

Your code runs on our machines. Not in a process you own, on a host you administer — on infrastructure we operate. That is the same bargain every hosted execution environment makes, and it is the reason your agent can keep working when your laptop is closed. It also means our security model is part of the product, not a footnote.

Each box is its own boundary. Two boxes do not share a filesystem, and one box cannot see another’s processes. The exact boundary — what is isolated from the host, what is shared, what egress rules apply — is documented here in full when the box ships, rather than summarised now and corrected later.

The box does not phone home on your behalf. We do not read what you run in it. We keep the operational metadata needed to run the machine — its state, its resource use, when it was last touched — and we keep it for the retention window described in the data handling document.

What a box is not

  • It is not a place to keep things. It is disposable. Use it for work, take your results out, destroy it.
  • It is not a development environment for your team. It is single-tenant, yours, and disposable. Shared team environments are a different thing.
  • It is not a place to run untrusted code safely enough to skip review. Isolation here is a real boundary, not a guarantee. Treat what you run in it with the same care you would give a container you started yourself.
  • It is not the specification pipeline. The box is where work happens. The specification-driven pipeline — the platform drafting a specification, you approving it clause by clause, and the build running from the approved snapshot — is under construction, and it will run inside this same kind of machine.

Frequently asked questions

Do I need an account to use a box?

The command talks to the platform API directly. The first version does not require signing in — if you can reach the API, you can create a box.

What can I install inside it?

Whatever the base image’s package manager supports. The default image ships with the usual build tooling; anything else you need, you install yourself, and it persists for as long as the box lives.

How do I get my code in and out?

Over SSH, using the tools you already have — scp, rsync, git clone, or a mount. The proxy carries all of it, so nothing needs a public port.

What happens to my files when the box is destroyed?

They are gone. Destruction is not a soft delete. Pull anything you want to keep out before you destroy a box, or let it be reclaimed and take it from the snapshot.

Can more than one person use the same box?

No. A box belongs to whoever created it. Sharing a box with someone else means sharing the credentials, which means you have both lost the isolation boundary that made it useful.

Next: what is available now, and what is being built.

Next