Enter your email and use the single-use link. There is no password to create.
2
Choose a tool
Open the session picker and select an agent, a plain Debian shell, or the free SSH
client.
3
Reconnect later
Close the tab whenever you like. Reopen the session to attach to the same tmux state.
02 · Coding agents
Bring the provider account you already use.
Terminalbox supplies the Linux environment and persistent terminal. Agent usage comes from
your Claude, ChatGPT, Gemini, or other provider account and remains subject to that
provider's limits.
Choose the agent template when creating a session.
Follow the sign-in link printed by the CLI.
Return to the terminal and paste a code if the provider asks for one.
Keep provider credentials inside your persistent Terminalbox home directory.
03 · Files and workspace
One home directory across your sessions.
Your plan's storage quota applies to the persistent home directory shared by your
Terminalbox sessions. Repositories, tool configuration, and shell history remain when you
detach or end an individual session.
Files
Upload, download, rename, and organize files from Dashboard → Settings → Files.
GitHub
Connect the GitHub App, choose repositories, and clone them into your workspace.
Dotfiles
Point Terminalbox at a public dotfiles repository and apply it to your home folder.
Environment
Save environment variables that should be injected when new sessions launch.
04 · SSH client sessions
Connect from Terminalbox to your servers.
The free SSH template is an outbound client: it opens a persistent browser terminal, then
runs SSH from that terminal to a host you control.
Open Dashboard → Settings → SSH.
Add a host name, hostname, user, port, and optional private identity.
Use quick connect or create a new SSH session from the session picker.
05 · Terminalbox CLI
Attach from a local terminal too.
Install the CLI on macOS or Linux:
curl -fsSL https://terminalbox.ai/install.sh | sh
Create a token under Dashboard → Settings → API tokens, then authenticate and inspect your
sessions:
terminalbox login
terminalbox list
terminalbox create codex
terminalbox attach <slug>
detach leaves the remote session running. stop ends and deletes that
session.
06 · Session lifecycle
Know what each action does.
Close the tab or detach
Paid containers continue running. A free SSH container pauses after six detached hours
and wakes automatically on the next attach.
Free SSH session paused
Compute is stopped, but the session still counts toward the one-session cap and files in
the persistent workspace remain.
End session or CLI stop
The individual container is deleted. Files in the shared home directory remain.
Cancel subscription
Paid sessions remain available until the end of the billing period, then become
suspended.
Delete account
Account deletion removes the account and its Terminalbox-managed workspace data.