Introduction
What Gitterm is, who it is for, and where to go next.
Gitterm gives your coding agents more computers, from the cloud providers you choose: sandboxes for the agent on your laptop, and cloud workspaces for agents that run in the cloud. Gitterm does not run its own machines. Every sandbox and workspace runs on a provider such as E2B, Daytona, Vercel or AWS, and Gitterm sits in between, so you can switch providers without changing how you work. This page explains both and points you to the right page to start.
Two products
Sandboxes, for the agent on your laptop. The sandbox plugin for OpenCode (@gitterm/opencode-sandbox) gives your local agent a set of sandbox_* tools. The agent uses them to run builds, tests, and preview servers in a remote sandbox. The conversation and your checkout stay on your machine. A sandbox runs no coding agent and receives no model credentials. See Sandboxes overview.
Cloud workspaces, for agents that run in the cloud. A cloud workspace runs OpenCode, or T3 Code (which drives Codex and Claude Code), on a remote provider. You open it in the browser or connect from a local client, so you can keep working from any device with your own model keys. You can also move a local OpenCode session into a workspace with the /cloud command from @gitterm/opencode-cloud. See Cloud workspaces.
Who it is for
- You use OpenCode locally and want heavy or slow commands to run on another machine, without handing the conversation to a remote agent.
- You want an agent that keeps running when your laptop is closed, or that you can reach from another device.
- You want to run Gitterm yourself. It is open source and self-hostable; see Self-hosting.
Who pays for compute
Sandboxes work without a Gitterm account. Use your own provider key (a direct account) and the provider bills you, or use your Gitterm plan (a managed account). Cloud workspaces always run through a Gitterm account. See Managed and direct accounts.
Where to go next
- Quickstart: run your first remote command, or start a cloud workspace.
- Concepts: the terms these docs use, on one page.
- Sandbox setup: install the plugin, add an account, and set approvals.
- Sandbox plugin reference and Cloud plugin reference: every option, variable, and command.