Conductor Cloud launched at the end of July 2026 and is included with Pro, Teams, and Enterprise. A cloud workspace runs in a Vercel Sandbox in us-east-1 with 8 vCPUs, 16 GB of RAM, and 32 GB of ephemeral NVMe storage, on Amazon Linux 2023 with a common toolchain preinstalled. Agents continue running after you disconnect, until the sandbox sleeps. Three differences from local matter: chat messages in cloud workspaces are stored on Conductor servers where local ones are not, cloud workspaces support GitHub only where local supports GitLab too, and cloud compute is currently unmetered but Conductor has said usage-based pricing is planned. There is no self-hosted or bring-your-own-cloud option yet.
- Cloud is the paid tier's real content. It is what Pro at 50 dollars a month actually buys.
- Sandbox specs are published: 8 vCPUs, 16 GB RAM, 32 GB ephemeral NVMe, Amazon Linux 2023, us-east-1.
- Cloud chat messages are stored on Conductor servers. Local workspaces are not, and Conductor says so plainly.
- Cloud is GitHub only. GitLab and Bitbucket work locally but not in a cloud workspace.
- Compute is unmetered right now, and that is stated as temporary. Usage-based pricing for cloud compute is planned.
- Still bring your own model credentials. Cloud changes where the agent runs, not who pays for its tokens.
What a cloud workspace is
A local Conductor workspace is a git worktree on your Mac with an agent process inside it. A cloud workspace is the same shape, except the worktree and the agent live on a remote machine. You still drive it from the Mac app, and the workspace still has a branch, a chat, a diff, and a review flow. The difference is that closing the laptop does not stop the agent.
That single property is what people are usually buying. A long refactor, a broad test-writing pass, or a dependency migration can run for an hour or more, and an agent that dies when your machine sleeps is an agent you have to babysit. Remote execution converts a foreground task into a background one. It is the same argument behind cloud agents generally, discussed in autonomous coding agents, applied to an agent CLI you already own rather than to a vendor's own model.
The machine you get
Conductor publishes the sandbox specification, which is more than most vendors in this category do. Cloud workspaces run on Vercel Sandbox, built with Conductor in collaboration with Vercel, in the us-east-1 region.
| Property | Value |
|---|---|
| CPU | 8 vCPUs |
| Memory | 16 GB RAM |
| Storage | 32 GB ephemeral NVMe |
| Operating system | Amazon Linux 2023 |
| Region | us-east-1 |
| Preinstalled runtimes | Node.js 24, npm, pnpm, Python 3 |
| Preinstalled tools | git, GitHub CLI, jq, ripgrep, Git LFS, tmux, Vim, Google Chrome |
| Lifetime | Runs while active, sleeps when idle; storage is ephemeral |
Two consequences follow from that table. First, the storage is ephemeral, so a cloud workspace is not a persistent development machine in the way a long-lived VM is. Anything that must survive belongs in the branch or in a service, not in the sandbox filesystem. Second, us-east-1 is the only region named, which is a real constraint if data residency is a requirement rather than a preference.
Chrome being preinstalled is a small detail with a large implication: browser-driven verification works, so an agent can start a dev server and check its own work rather than reporting a change it never ran.
The three things that change when you go remote
These are documented by Conductor rather than inferred, and each one has caught someone out.
Your chat messages get stored
Conductor states that unlike local sessions, chat messages sent in cloud workspaces are stored on Conductor's servers, and that with local Conductor it never accesses your coding inputs or outputs. If your reason for choosing a local-first tool was that nothing leaves the machine, the cloud tier is a different product on that axis, not an extension of the same one.
GitLab and Bitbucket stop working
Cloud workspaces are GitHub only. Conductor's documentation says other git hosts are not supported yet. Local workspaces do support GitLab, so a GitLab shop can use Conductor but cannot use the tier it pays for.
The compute bill is deferred, not absent
Conductor's FAQ says there is no additional fee for cloud workspaces right now, and that it plans to introduce usage-based pricing for cloud compute in the future. Pro's allowance is described only as a quantity of cloud workspace hours with no published number. Both of those are things to ask about before building a workflow that depends on cheap remote compute.
What cloud does not change
The model bill is the big one. Conductor's pricing FAQ addresses cloud specifically: you bring your own subscriptions or API keys for cloud workspaces just as you do locally. Remote execution moves the process, not the invoice. A cloud workspace burning Opus tokens for an hour bills your Anthropic account, and if that account is a Claude Max subscription it consumes the same weekly quota your local sessions do. Watching that quota is a separate problem, covered in Claude Code usage limits.
The harness set does not change either. Cloud workspaces run the same four agents, with the same uneven feature matrix described in what Conductor is. Plan mode and checkpoints remain Claude Code and Codex only whether the workspace is local or remote.
One thing cloud adds that is easy to miss: cloud sandboxes ship with a conductor command preinstalled so an agent can create workspaces, start chats, and send follow-up messages on its own. Combined with the beta HTTP API and hosted MCP server, that is the closest thing Conductor has to programmable orchestration, since there is no CLI you can install on your own machine.
When remote is the wrong answer
Remote sandboxes are not strictly better, and the honest cases against are specific.
- Your repository needs local services. A sandbox in us-east-1 cannot reach a database on your laptop, a VPN-only staging environment, or a local device. Setup scripts can install dependencies; they cannot conjure your network.
- Your git host is not GitHub. This is a hard stop for cloud workspaces today.
- Prompt content cannot leave your machine. Cloud chat storage is a policy change, not a configuration flag.
- You wanted parallelism, not persistence. Free already gives unlimited local parallel workspaces. If your agents finish in ten minutes and you are at your desk anyway, cloud solves a problem you do not have.
- You need the session on your phone more than on a server. These are different requirements. Remote execution keeps a session alive; it does not by itself let you read a plan and approve it from a phone.
Questions people ask
Is Conductor Cloud included in the free tier?
No. Conductor Cloud requires Pro, Teams, or Enterprise. The Free tier is local-only, though it does allow unlimited parallel local workspaces.
How much cloud compute does Pro include?
Conductor does not publish a number. The pricing page describes it only as a quantity of cloud workspace hours. Conductor separately says cloud compute is not billed as an additional fee right now and that usage-based pricing is planned, so the allowance may become the meaningful figure later.
Where does Conductor Cloud run my code?
In a Vercel Sandbox in the us-east-1 region, with 8 vCPUs, 16 GB of RAM, and 32 GB of ephemeral NVMe storage on Amazon Linux 2023. No other regions are documented as of August 2026.
Does Conductor store my conversations in the cloud?
In cloud workspaces, yes. Conductor states that chat messages sent in cloud workspaces are stored on its servers, in contrast to local sessions where it says it never accesses your coding inputs or outputs. That is a deliberate difference between the two modes.
Can I use Conductor Cloud with GitLab?
No. Cloud workspaces support GitHub only, though local workspaces do work with GitLab. Conductor says support for other git hosts is not available yet.
Can I run Conductor Cloud in my own AWS account?
Not as of August 2026. Conductor says it is building a self-hosted cloud offering but that it is not available at the moment, so bring-your-own-cloud and on-premise deployment are roadmap items rather than options.
Sources
Every figure above was read from these pages on August 2026. Vendors reprice without notice; if you find a stale number, tell us.