An always-on operator shell
Paid workspaces continue running while you are detached. Return through the browser or Terminalbox CLI to the same files, processes, and tmux session instead of leaving a laptop awake.
Start with OpenClaw installed in an isolated, persistent Debian workspace. Keep the CLI and gateway processes running when your laptop closes, while you retain responsibility for providers, channels, access policy, updates, and backups.
$ claude
Claude Code · /workspace/repo
> Refactor data loader to stream results and add tests.
I'll refactor the data loader to use a streaming approach and add comprehensive tests.
Plan
Edit src/loader/stream.ts
+ 142 − 68
Edit test/loader/stream.test.ts
+ 211
Bash npm test
> 32 passed (1.2s)
✓ All tests passing.
>
Paid workspaces continue running while you are detached. Return through the browser or Terminalbox CLI to the same files, processes, and tmux session instead of leaving a laptop awake.
Each OpenClaw terminal runs in its own unprivileged container with CPU, memory, process, and storage limits. It is a single-operator environment, not a shared gateway for mutually untrusted users.
OpenClaw and the Linux toolchain are prepared, but the shell stays yours. Configure the model provider, plugins, channels, gateway authentication, and private access path for your own threat model.
Base provides one persistent OpenClaw terminal with 2 vCPU, 4 GB RAM, and 50 GB of storage. That exceeds OpenClaw’s documented 2 GB recommendation for a typical gateway using hosted models.
Launch the OpenClaw template, connect your own model provider, and configure only the channels and tools you intend to trust. Model subscriptions, API usage, and channel accounts remain separate.
Keep the gateway on loopback by default and run OpenClaw’s security audit. Terminalbox does not publish a gateway port or configure a private Control UI tunnel for you.
No. Terminalbox manages the persistent Linux terminal and its isolation. You operate OpenClaw: onboarding, providers, channel policies, gateway authentication, updates, plugins, and workspace backups remain your responsibility. Choose a fully managed OpenClaw provider if you do not want that operator role.
An always-on host keeps the gateway and channel connections available through laptop sleep, travel, and local restarts. OpenClaw’s own documentation recommends a VPS or dedicated host when reliability and isolation matter.
Terminalbox does not expose the OpenClaw gateway on a public URL. Paid panes provide inbound SSH for shell and remote-command sessions, but the SSH gateway rejects TCP forwarding, so it does not create a Control UI tunnel. Keep OpenClaw on loopback by default and confirm a supported private access design before buying if the UI is required.
No. The Terminalbox price covers the hosted terminal and persistent workspace. OpenClaw model providers, subscriptions, API usage, messaging channels, and third-party services are billed and governed separately.
Files persist in the workspace while the subscription is active, but Terminalbox does not currently promise customer-initiated restores or a backup SLA. Export the OpenClaw state and workspace you need to recover.
That is not the intended security model. OpenClaw recommends one trusted operator boundary per gateway. Use separate Terminalbox workspaces and separate gateways when users should not share delegated tool authority.
No. Terminalbox is an independent hosting product. OpenClaw controls its releases, security guidance, provider support, and gateway behavior.
Plans start at €6 per month for one hosted coding-agent terminal.