The OpenCode host stays available
The paid workspace and its processes continue while you are detached. Close the browser or put your laptop to sleep, then reconnect to the same tmux-backed terminal from another device.
▍ OpenCode hosting
Keep OpenCode running.
Run the actual OpenCode TUI in a prepared Debian workspace that stays online. Return from any browser or the Terminalbox CLI without operating a VPS.
- €6/month flat price
- 2 vCPU · 4 GB RAM · 50 GB
- OpenCode preinstalled
opencode-review
$ opencode
OpenCode · /workspace/repo
> Review the data loader and add regression tests.
I’ll inspect the loader, tighten the streaming path, and add regression tests.
Plan
Update loader to async generator Add backpressure handling Write unit tests Update integration tests Run test suiteEdit src/loader/stream.ts
+ 142 − 68
Edit test/loader/stream.test.ts
+ 211
Bash npm test
> 32 passed (1.2s)
✓ All tests passing.
>
What changes
The terminal becomes a place you return to.
Start in a prepared Linux shell
OpenCode, Git, Node.js, common package managers, networking, and tmux are already installed. Your project files and OpenCode state live in the persistent home volume.
The hosting bill stays predictable
Base costs €6 per month for one persistent OpenCode terminal with 2 vCPU, 4 GB RAM, and 50 GB of storage. Terminalbox does not add per-minute compute charges.
How it works
From sign-in to a persistent session.
- 01
Start one Base workspace
Use Base for one OpenCode environment. Choose Pro or Max only when several coding-agent terminals and more shared storage are already useful.
- 02
Connect your model provider
Launch the OpenCode template and use OpenCode’s provider flow. Enter credentials inside your own terminal; model access, subscriptions, and API usage remain separate from Terminalbox hosting.
- 03
Detach and return from another device
Clone the repository, run OpenCode, and leave the session when you are done. Reopen it through a browser or the Terminalbox CLI without rebuilding the workspace.
Before you start
Questions worth answering.
What exactly does Terminalbox host for OpenCode?
Terminalbox hosts OpenCode’s terminal interface in a persistent Linux workspace with browser-terminal and Terminalbox CLI access. It does not expose or claim to host OpenCode’s native web interface.
Are OpenCode models or provider charges included?
No. Terminalbox charges only for the hosted environment. You connect OpenCode Zen or another provider supported by OpenCode, and that provider controls account access, limits, billing, and model availability.
Can I use OpenCode web instead?
Yes. OpenCode’s official web command is free and is the right choice when your own computer or server can remain online and you want its native browser interface. Terminalbox is for the terminal workflow when you want the host and tmux session to persist independently of your laptop.
Can Terminalbox publish an OpenCode web or server port?
Not today. Terminalbox does not provide a public OpenCode server URL or an inbound SSH endpoint. Buy it for the hosted terminal and Terminalbox CLI attachment, not for the native OpenCode web UI or a custom public service.
When is a normal VPS the better choice?
Choose a VPS when you need root access, firewall control, a dedicated public IP, custom ports, or the native OpenCode web interface on your own domain. Terminalbox is a managed container and intentionally does not provide host-level control.
What survives when I close the browser?
While the paid subscription is active, the workspace, persistent home directory, running processes, and tmux session continue. Reopening the terminal attaches to the same workspace.
Is Terminalbox affiliated with OpenCode?
No. Terminalbox is an independent hosting product. OpenCode controls its software, provider support, releases, documentation, and model integrations.
Persistent by default
Start here. Pick it up anywhere.
Plans start at €6 per month for one hosted coding-agent terminal.