Give your agents more room to work.

Cloud sandboxes for the agent on your laptop, or a cloud workspace for the whole agent. From the provider you choose, and you can switch any time.

Extend your laptop

OpenCode on your laptop runs tests, builds and previews in cloud sandboxes.

$ opencode plugin add @gitterm/opencode-sandbox

Then fill in your config. No Gitterm account needed.

Run agents in the cloud

OpenCode, Codex or Claude Code in a cloud workspace. Reach it from your phone or Slack.

$ opencode plugin add @gitterm/opencode-cloud

Then sign in and type /cloud, or start one in the browser.

Or let your agent set it up

Set up Gitterm for me. Read https://gitterm.dev/llms.txt first and follow the docs it links to. Don't guess at commands or config.

Extend your laptop

Your agent can attach sandboxes from any of these. The demo moves through them on its own, or pick one to see it.

Sandboxes attach as the agent needs them.

opencode · ~/code/shop

OpenCode died

Your Mac ran out of memory mid-run.

Build · Claude Opus 5.5 Anthropic

Activity Monitor

CPU6%

Memory4.8 of 16 GB

Battery92%, 7h left

opencodeidle

Waiting for a request.

E2B sandboxsbx_7f3a2c

No sandbox yet

Gitterm plan, 60 minute lifetime

3000-7f3a2c9e41d8b0a5c3f2.gitterm.dev

No preview yet

Checkout

Linen overshirt, M€89.00

Canvas tote€24.00

AUTUMN10Apply

This code expired on 31 October.

Total€113.00

9:415G

18:42

Tuesday, 3 November

Gitterm

Run tests and preview checkout

E2Bworkspace

I have to leave for a train. Keep going and I’ll check from my phone.

Cloud handoff41 messages

Restored here. Tests pass and the checkout preview is up.

Looks good. Open the PR.

Opened PR #482 from checkout-coupons.

Ask anything…

The demo session needs JavaScript. In short: the agent creates an E2B sandbox, syncs your files, runs the tests there, fixes a failing test locally, starts a preview, and then /cloud moves the session to a cloud workspace you can open from your phone.

What the plugin does

The same session as above, one step at a time.

Step 1 of 5

Your agent stays on your laptop

Add the plugin and OpenCode gets sandbox tools. The conversation and your model keys stay on your machine.

Step 2 of 5

It borrows a machine when it needs one

The agent starts a sandbox on the provider you set and syncs your working tree. Ignored files like .env stay home. Once it has saved a setup snapshot, the next sandbox starts with dependencies already installed.

sandbox_createsandbox_sync

Step 3 of 5

The heavy work runs there

Tests, builds and dev servers run in the sandbox. The agent gets the output when a job finishes, or checks back on a long one, while your laptop stays idle.

sandbox_execsandbox_job

Step 4 of 5

Results come back to you

A port becomes a preview URL you can open. Files changed in the sandbox only land in your checkout when the agent applies them.

sandbox_previewsandbox_apply

Step 5 of 5

Or take the whole session with you

Add the cloud plugin and type /cloud. The conversation, your unpublished commits and, if you choose, uncommitted changes move to a cloud workspace. Pick it up from your phone, a browser or OpenCode desktop. Your laptop copy stays as it was until you bring the session back with /cloud-return.

Your key, our plan, or your server

Set one account in the plugin options. Add limits to any of them, so a busy agent cannot run up a surprise bill.

Bring your own provider key

No Gitterm account needed. The key comes from your environment and the provider bills you directly.

"options": {
  "provider": "e2b",
  "apiKey": "{env:E2B_API_KEY}"
}

Use your Gitterm plan

No provider account needed. Sign in with gitterm login; sandboxes count against your plan, and Gitterm stops anything that outlives its deadline.

"options": {
  "size": "medium"
}

Use your own Gitterm

Point at a self-hosted server. It uses its default provider; add provider to pick another one it offers.

"options": {
  "serverUrl": "https://git.acme.dev"
}

Also in OpenCode desktop

Same plugin, same tools. Every sandbox call shows up as a row you can open, and a session you moved with /cloud pairs to the app with a one-time link.

Run tests and preview checkout

E2B workspace · checkout-couponsRun tests and preview checkoutSession changes 2 files

Ask anything, / for commands, @ for context…

Build Anthropic / Claude Opus 5.5

Run agents in the cloud

Send sessions to the cloud. Bring them back.

Move an OpenCode session to a cloud workspace with /cloud, or start Codex or Claude Code in a new one from T3 Code. They keep running on their own, and your laptop is free for whatever is next. /cloud-return brings a session back whenever you want it.

Works with

OpenCode

Move a session with /cloud, back with /cloud-return

T3 Code

RunsCodex andClaude Code

Your laptopCPU 92%

Cloud workspaces

Take it with you, then bring it back

Move an OpenCode session to the cloud, keep the agent going on your phone, in a browser or on another computer, then pull the session back to your laptop whenever you like, finished or not.

The whole agent session travels: its conversation, and the checkout it works in, with commits and uncommitted changes. Anything you changed on your laptop in the meantime is kept.

Keep a snapshot as you return, and the next /cloud starts with the setup done.

Your laptop
/cloud
Gitterm
/cloud-return
Your laptop

Drive it from anywhere

A workspace keeps running while you are away. Check in from your phone, hand work over in Slack, or start runs from your own code.

Your phone or browser

Scan a QR code to open the workspace in the OpenCode app on your phone, or open it in any browser. Pause it when you are done and pick up later.

Pairing linkws-7k2.gitterm.dev/auth/connect/7QK4M25 min

acme/shopT3 Code on E2BiPhone appRunning
acme/adminCodex in T3 Code on VercelAndroid appRunning
acme/apiOpenCode on RailwayWeb appRunning
acme/docsOpenCode on DaytonaDesktop appRunning

Idle workspaces pause on their own.

Slack and Discord

Mention @gitterm in a channel. It works in a cloud workspace for that repo and answers in the thread. Self-host the bot from one Docker image.

Thread# shop-dev

Ada6:40 PM

@gitterm the checkout test is flaky again, can you take a look?

👀 1

2 replies

gittermAPP6:41 PM

On it. Working in acme/shop in a cloud workspace.

gittermAPP7:03 PM

Fixed the clock dependency. 20 runs passed. @Ada

GitHub

Fix flaky checkout test #482acme/shop, 1 commit, +12 −3

✅ 2🙌 1

Reply…

Your own code

The SDK creates a workspace, starts a run and waits for the result. Use it from scripts, CI or your own tools.

const { workspace } = await client.workspaces.create({ repo: "https://github.com/acme/shop" });
const run = await client.runs.create({ workspace, prompt: "Fix the flaky checkout test." });
const { finalText } = await client.runs.result(run);

Everything a workspace can do

Start one from the dashboard, the CLI or the SDK, or let /cloud make one for you.

Pause and resume

Stop paying for compute, keep the workspace, pick up where you left off.

Share a live preview

Expose any port as a private URL, or make it public for webhooks and demos.

Attach your terminal

Open it in your local OpenCode TUI with one command, or in the T3 Code desktop app.

Connect from any device

Same workspace in your browser, OpenCode desktop or your phone.

Set keys once

Model keys are saved once and reused in every workspace, never pasted again.

Script it

Create workspaces with the SDK. Manage them with the CLI or the SDK.

Give your agents more computers.

Add the plugin to OpenCode, or start a cloud workspace. Open source and self-hostable.

$ opencode plugin add @gitterm/opencode-sandbox

Start a cloud workspace View on GitHub