How Conductor moved parallel coding agents from the laptop to the cloud with Vercel Sandbox

Conductor on VercelMultiple parallel coding agents running at scale in the cloudModel-agnostic, works with Claude Code, Codex, and other coding agentsUsed by engineering teams at Notion, Linear, Ramp, and Life360Interacting with a single coding agent feels natural, and Conductor makes directing a fleet of agents just as intuitive. It's a GUI for spinning up multiple coding agents in parallel, each working on an isolated branch of your codebase at once.

You review their work, merge what works, and redirect the agents that need to keep iterating. Engineering teams loved it, but hardware was a real limitiation. Every agent ran on your machine, so the fan climbed, the CPU ran hot, and if you closed your laptop, the agents stopped. Charlie Holtz, co-founder and CEO of Conductor, spent time at Vercel before starting the company. He understands what developers lose when their environment imposes rules on how they can work.

Cloud Workspaces, Conductor's remote execution layer built on Vercel Sandboxes, removes the local hardware constraint. Developers can now spawn multiple agents and close the lid without interrupting work. Developers who adopted Conductor early felt the power. Notion's engineering team said, "It makes you feel like an octopus, where each one of your arms is working on something separately. "The demand for remote execution came quickly. Developers wanted more agents running longer, and local hardware was the ceiling.

For a six-person startup, going from local to cloud is a huge leap, and when the developers using Conductor work at companies like Linear and Ramp, the choice of provider isn't just a technical decision. It's a trust conversation with the people running their code on infrastructure they don't own. The team evaluated several sandbox providers, weighing fast spin-up and snapshot support alongside longevity and the depth of the support relationship. Conductor built Cloud Workspaces on Vercel Sandboxes.

When a developer opens a new workspace, agents spin up on a remote server instead of their local machine. The interface doesn't change. Holtz describes the result: "To our users it feels just like the local version of Conductor. They don't know the difference, which is amazing, and that's because Vercel Sandboxes are super fast. "Conductor already supports Claude Code, Codex and other coding agents, but they are model agnostic.

That means that no matter how often labs release updates, or what the next popular harness is, they can keep the same cloud layer underneath. As Holtz puts it: "The vibes shift every 3 months. Right now GPT-5. 5 has the vibes on its side, but that's going change in another few months. Being agnostic to the providers is the key, and we get that with Vercel. "Conductor's bet is on the interface: the one place to direct your agents, review their work, and decide what to merge.

With Vercel Sandbox, that interface goes wherever developers go. : is a multi-agent IDE for running coding agents in parallel, each on isolated branches of your codebase. Model-agnostic by design, it works with Claude Code, Codex, and other coding agents. About ConductorConductorRead moreThe journey from local to cloudRunning parallel agents in the cloudOne interface, whatever the frontier looks like next