Keep the right work in the right place.
Terminalbox lets you return to terminals from a browser. What persists depends on where the terminal runs and which action you take.
Two runtime locations
Swipe the comparison sideways on a small screen.
| Location | Files and tools | Availability |
|---|---|---|
| Your machine | Use the files and installed tools already on that macOS or Linux computer. | The computer must stay awake, online, and connected through its host agent. |
| Terminalbox cloud | Use a hosted Linux environment and persistent home directory shared by hosted sessions. | Paid sessions can keep running while the subscription is active; free SSH sessions have a pause policy. |
Detach and reconnect
Closing a browser tab detaches your viewer. It does not end a hosted session. A connected-machine shell can continue after detach when tmux is installed and the machine stays awake; without tmux, reconnecting opens a new login shell.
A free SSH session pauses after six detached hours and wakes when you reconnect. It still counts toward the one-session cap, and its files remain while paused. Its 5 GB total storage quota includes the environment and home. Paid cloud sessions continue running while the subscription is active.
Cloud files
The hosted home directory holds repositories, tool configuration, shell history, and uploads across hosted sessions. Your plan's total storage quota covers both this home directory and the hosted Linux environment, so available space for files is less than the listed total. A connected machine keeps its files on that machine; Terminalbox does not copy them into cloud home.
Use Dashboard → Settings → Files to upload, download, rename, and organize hosted files. The dashboard also offers GitHub repository setup, public dotfiles, and environment variables for new hosted sessions.
End a session
Ending a hosted session or using terminalbox stop <slug> deletes that individual
container. Files in the shared hosted home directory remain. Account deletion is initiated in Settings;
verify that hosted data deletion completed before relying on it as a data-erasure step.