Use your computer.
There is no infrastructure reason to buy Terminalbox.
Use the free official path →Official Remote Control server mode can start on-demand sessions from iPhone, Android, or any browser. It still runs on your computer. Pay for another host only when that machine cannot stay awake.
In a trusted project directory, sign in to Claude Code and run claude remote-control. Server mode can create multiple sessions on demand;
the process and its host must keep running.
There is no infrastructure reason to buy Terminalbox.
Use the free official path →Run server mode inside tmux or screen so it survives your SSH disconnect.
Review the DIY setup →Keep one managed Linux terminal online, then enable official server mode inside it.
Continue to the managed host →Your answers stay in this tab. Terminalbox records only that the router was used, never the choices themselves.
Anthropic’s current documentation distinguishes a local Remote Control session from a cloud web session. Both appear in the Claude app on iOS and Android, but the code runs in different places.
Run claude remote-control for an on-demand session server, or claude --remote-control for one interactive session. The connection uses outbound
HTTPS; no inbound port is opened.
Start from claude.ai/code or the Code tab in the mobile app. Anthropic runs the task in a cloud VM and can create a branch for review.
The laptop can be off. Official web quickstart ↗“Mobile” describes the control surface, not the execution host. Choose the environment before choosing the app.
| Question | Remote Control | Claude web | DIY VPS | Terminalbox |
|---|---|---|---|---|
| Where does the code run? | Your computer | Anthropic cloud VM | Your remote server | Managed Linux container |
| Keeps running when the laptop closes? | No | Yes | Yes | Yes |
| Phone interface | Claude app or claude.ai; server mode can start sessions | Claude app or claude.ai | SSH client or web terminal | Browser terminal |
| Full interactive shell | No; the shell stays on your computer | No; provider-managed task UI | Yes | Yes |
| Root or kernel control | Whatever your computer allows | No host control | Yes | No |
| Workspace source | Existing local files | Repository clone or CLI bundle | Clone, upload, or sync | Clone, upload, or sync |
Terminalbox is independent from Anthropic. “Claude” and “Claude Code” identify Anthropic’s products; no endorsement or partnership is implied.
Use Terminalbox when phone access must include the real terminal, background processes, interactive commands, and the same tmux state after every reconnect.
Compare persistent terminal plans →Yes. Run claude remote-control in a trusted project directory. Official server mode stays ready for connections and can create on-demand sessions from claude.ai or the Claude mobile app. The machine and the server-mode process must remain online.
Yes. Anthropic Remote Control and Claude Code on the web both work through the Claude mobile app. A browser terminal is another option when you need the full shell rather than only the provider conversation interface.
No execution happens while the computer is asleep or off because the Claude Code process remains on that computer. Remote Control reconnects after the machine is awake and online again. Use an existing always-on server or a hosted terminal only when the laptop-off requirement is real.
Use the provider cloud path when an isolated repository task and provider-managed environment are enough. It keeps running across device disconnects without requiring a separate Terminalbox subscription.
No. Terminalbox provides the hosted Linux terminal and persistence. You sign in with your own compatible Anthropic account, and Anthropic usage limits and charges remain separate.
No. Terminalbox intentionally does not provide root, kernel, or host-level network control. Choose a self-managed VPS when those capabilities are required.
We will recommend the official, DIY, or managed path that matches the actual dependency.