Close the lid. The agent keeps working.

A persistent cloud machine for Claude Code, Codex or Gemini CLI. Open the same session later from your phone, a browser or your own editor.

Workspaces › acme-apiOpen in VS Code · Snapshot · Sleep

Migrate billing to the new SDK

Claude Code has been working on this workspace since yesterday evening. The laptop that started it is closed.

Activity
maya opened a session from VS Codeyesterday 17:52
Claude Code prompt Move billing to the v4 SDK and keep the tests greenrecorded
maya disconnected, laptop closed18:40
Claude Code kept working: 214 tool calls, 31 files editedovernight
Claude Code ran go test ./...all passed
Claude Code tried git push --forceblocked by policy
maya reconnected from her phone07:55
Claude Code wants to run git push origin billing-sdk
Needs approval from mayaDenyApprove
State
Running
Template
node-22
Size
4 vCPU · 16 GB
Disk
50 GB, persistent
Sleeps
after 30 min idle
Access
SSH certificate, 15 min
Region
us-east
Project
payments
Running for
13:58:30

Agents work longer than laptops stay open. A workspace is a cloud machine that keeps your repo, your tools and the agent’s session running, so you can close the lid and pick the work up from any device.

FIG 0.1Nothing starts from scratch

Repo, branch, dependencies, caches and shell history are still there tomorrow.

FIG 0.2Any device is a way in

VS Code, Cursor, a terminal or your phone. The session stays on the workspace.

FIG 0.3Sleeps when idle

Hours count only while it runs. It wakes exactly as you left it.

One session,
every device

The agent’s session lives on the workspace, not on the machine you opened it from. Close the laptop, then follow along from your phone or another editor. Access uses certificates that expire in minutes, not keys left on disk.

See integrations →
Terminalssh acme-api
Certificate valid for 15 min
acme-api
claude --resume
session 7f2c attached
VS Codemaya’s laptop
Disconnected at 18:40
acme-api
the agent kept working
214 tool calls since
Browsermaya’s phone
Connected at 07:55
acme-api
reading the overnight diff
approved a push
Cursormaya’s desktop
Connected at 09:10
acme-api
same session, another editor
diff open for review

Picks up
where you left it

The disk is persistent and the machine sleeps when nobody uses it. Start and stop on a schedule, snapshot before a risky change, and start everyone from the same template.

See templates →
Workspaces › Team6 workspaces · 1,000 vCPU-hours each, pooled
WorkspaceOwnerStateTemplateSize
acme-apimayaRunningnode-224 vCPU13 h
web-appsamAsleepnode-222 vCPUidle 2 h
data-jobsleeScheduledpython-3.128 vCPUweekdays 08:00
mobiledanaRunningnode-224 vCPU2 h
infrajoAsleepgo-1.252 vCPUidle 1 d
docskimAsleeppython-3.122 vCPUidle 3 d

Governed like
every sandbox

The agent in a workspace runs under the same policy as one in a sandbox. Risky commands wait for a person, secrets come from Vault in memory, and every session and change lands in the audit log.

How we secure it →
Policy › payments
Templates
node-22, python-3.12
Largest workspace
8 vCPU
Sleep after
30 min idle
Agents
Claude Code, Codex
Ask first
git push, gh pr create
Block
git push --force
Secrets
from Vault, in memory
Audit logHash-chained · export
TimeWhoActionTargetEntry
07:55:12mayaworkspace.connectacme-api · phone3e81a0
07:58:40maya via Claude Codetool.blockedgit push --forcec4f219
07:59:02mayaapproval.grantedgit push origin billing-sdk9b07de
08:00:00schedulerworkspace.startdata-jobs51ac3f
09:12:44samworkspace.wakeweb-app0d6e92
09:30:10lee@acme.devpolicy.updatepayments · sleep after 30 mina7f3c1

Included in
your plan

Workspaces draw from the same monthly vCPU-hours as sandboxes and build hosts. Workspaces run in the US or Europe, the region you pick for each one. On Enterprise they can also run in your own AWS account.

See pricing →
Free
Not included

Sandboxes only.

Pro
Workspaces

750 vCPU-hours a month, shared with sandboxes and build hosts.

Team
Workspaces

1,000 vCPU-hours per member, pooled across the team.

Give your agent a desk
that never closes

Workspaces come with Pro and up. Start free, upgrade when you’re ready.

A Firecracker microVM for every runNo network by defaultPause and resume with state keptVault keeps secrets out of promptsSSO, roles and audit logBring your own cloudWorks over MCP and the CLI