Start in a real Linux terminal.
Choose an agent template, sign in with the provider account you already use, clone your repository, and work through the same CLI interface you know.
A local process pauses when its machine sleeps. Terminalbox moves the terminal to a hosted Linux workspace, so your coding agent can keep going and the same interactive shell is waiting on your next screen.
The process and project live on Terminalbox—not on the laptop.
A terminal multiplexer can survive a dropped connection, but it cannot make a sleeping laptop execute code. Terminalbox provides the always-on machine and puts every agent pane inside tmux, so both parts of the problem are covered.
Choose an agent template, sign in with the provider account you already use, clone your repository, and work through the same CLI interface you know.
Close the browser, switch networks, or shut the laptop. The workspace, agent process, files, development servers, and tmux session remain on the host.
Attach from another browser or the Terminalbox CLI. You see the output produced while you were away and can type the next instruction immediately.
No. Paid coding-agent panes run on Terminalbox’s hosted Linux machine. Your local device is only the screen and keyboard you use to attach.
Yes. Each pane uses a persistent tmux session. Reopening the pane attaches to the running process and its terminal state rather than starting a replacement chat.
You bring the Claude, OpenAI, Gemini, or other provider account you already use. Terminalbox charges for the hosted terminal and workspace, not model usage.
Cancel anytime. No metered Terminalbox compute. Your provider subscription stays yours.