8 Conductor Cloud alternatives after the November 2026 shutdown
Published
Summary
Conductor announced on November 4, 2026 that it is joining Meta, and Conductor Cloud shuts down on November 20, 2026. These eight alternatives are for teams that ran Claude Code, Codex, or Cursor agents in Conductor Cloud and need another place for that work to run in the cloud.
Why teams look
What happens to Conductor Cloud
Conductor announced that it is joining Meta. Its announcement on conductor.build sets the following schedule for Conductor Cloud, the hosted version where agents ran in shared cloud workspaces. The local Mac app is not affected by these dates.
- November 4, 2026: new sign-ups stop, and active subscribers get a refund.
- November 13, 2026: Conductor Cloud becomes read-only. You can read old chats and export data, but you cannot send new messages.
- November 20, 2026: Conductor Cloud shuts down, and Conductor begins deleting cloud user data.
- Early 2027: the local Mac app stops getting new models and critical bug fixes and begins winding down.
- To keep your data, push every branch, then use Settings → Account → Export data, or right-click a cloud workspace and choose Transfer to local.
8 Conductor Cloud alternatives
Conductor Cloud alternatives at a glance
The table compares each tool by what it actually is, where the agent runs, and who it fits. Product surfaces change quickly in this category, so verify pricing and deployment details against each vendor before committing.
| Tool | Product model | Where work runs | Best for |
|---|---|---|---|
| Replicas | Cloud agent platform for delegated engineering work | One isolated Linux VM per task; dedicated or self-hosted for enterprise | Teams that want shared cloud workspaces running Claude Code, Codex, or Cursor, started from the app, Slack, Linear, GitHub, or automations |
| Paradev | Open-source workspace for running several coding agents in parallel | Your Mac or a machine you add; cloud workspaces in early access | Engineers who want a desktop app like local Conductor, with parallel agents in Git worktrees |
| Tembo | Cloud platform for running coding agents | Tembo cloud or self-hosted | Teams that want managed cloud orchestration across several coding agents |
| Cursor | AI-native code editor with Cloud Agents | Local editor; Cloud Agents run in isolated VMs | Teams that ran Cursor agents and want Cursor's own cloud agents |
| Claude Code | Provider-native coding agent from Anthropic | Local terminal and IDE, plus Anthropic-hosted web sessions | Teams that ran Claude Code and want Anthropic-hosted sessions |
| OpenAI Codex | Provider-native coding agent from OpenAI | Local CLI and IDE, plus OpenAI-hosted cloud tasks | Teams that ran Codex and want OpenAI-hosted cloud tasks |
| GitHub Copilot coding agent | Agent built into GitHub | GitHub Actions runners | Teams that want issue-to-pull-request automation inside GitHub |
| Devin | Autonomous software engineer | Managed Devin cloud sessions | Teams that want one packaged agent instead of choosing a harness |
Replicas: managed parallel engineering work with harness choice
Replicas is a cloud agent platform for delegated engineering work. Assign features, refactors, bug fixes, or tests; the agent plans the work, changes code, runs checks, and returns a pull request or investigation for your team to review. Independent tasks can run in parallel, and engineers can inspect and steer each session.
Work starts from wherever it already lives: a Linear issue, a Slack thread, a PR comment, a failed CI run, a schedule, a webhook, or the dashboard. Because Replicas is harness-agnostic, you can use existing Anthropic, OpenAI, Bedrock, or other inference credentials where supported instead of buying model usage through one vendor.
Developer is $50 a month and Team is $200+; each includes workspace usage equal to its price. Every organization starts with $100 of free usage and no credit card. Enterprise plans add SOC 2, SCIM, audit logs, static egress IPs, and single-tenant or self-hosted deployment.
Paradev
Paradev, formerly Superset, is an MIT-licensed desktop app that runs Claude Code, Codex, Cursor Agent, and other CLI agents side by side, each in its own Git worktree. It also has a CLI, an SDK, and an iPhone app.
Its documentation describes cloud workspaces as early access on paid plans, so check whether they are available to your account if you need agents to keep running while your laptop is closed.
Tembo
Tembo is the closest orchestration competitor to Replicas. It runs several third-party agents in the cloud, integrates with GitHub, Slack, and Sentry, and offers self-hosting for enterprise buyers.
Evaluate the two on harness coverage, environment configurability, trigger surfaces, and whether you can bring your own inference paths.
Cursor
Cursor is the most widely adopted AI-native editor. Its agent mode, Cloud Agents, Bugbot review, and CLI make it a full ecosystem for teams happy to standardize on Cursor for both interactive and background work.
The trade-off is ecosystem commitment. Model usage is metered through Cursor, and the cloud agent is Cursor's agent. Teams that already trust Claude Code or Codex, or that want to reuse existing inference contracts, tend to look for a workspace layer instead.
Claude Code
Claude Code is the harness many engineering teams already trust for daily work. It runs in the terminal or IDE, supports plans, hooks, skills, and MCP servers, and is often the reference point in agent comparisons.
Anthropic also offers hosted Claude Code sessions that run independently in parallel and can return pull requests for GitHub repositories. Replicas is another way to run Claude Code in the cloud, with a choice of supported harnesses and shared environment configuration across them.
OpenAI Codex
Codex gives ChatGPT subscribers a coding agent in the terminal, IDE, and browser, with cloud tasks that run in OpenAI-managed sandboxes and open pull requests.
Compare OpenAI-hosted tasks with running the Codex CLI through Replicas if your team wants to choose among several coding harnesses in the same platform.
GitHub Copilot coding agent
Copilot's coding agent can be assigned a GitHub issue, work in a GitHub Actions environment, and open a pull request for review. For teams already paying for Copilot, it is the lowest-friction way to try delegated work.
Execution is bound to GitHub Actions and the GitHub surface. Teams on GitLab, teams that need browsers and long-running services in the agent's environment, or teams that want to choose the harness look elsewhere.
Devin
Devin from Cognition defined much of the autonomous software engineer category. It ships with its own workspace, Playbooks for repeatable tasks, Slack and Linear intake, and enterprise administration.
Devin is a single agent with a single working model. That is a feature for teams that want one vendor to own the whole experience, and a limitation for teams whose engineers already have strong preferences about which harness does the work.
Migration
How Conductor Cloud concepts map to Replicas
Most of what a Conductor Cloud organization configured has a direct counterpart in Replicas. The main structural difference is that Conductor Cloud has one Cloud Computer per organization, while Replicas lets you create many environments, each with its own repositories, variables, and setup.
| Conductor Cloud | Replicas |
|---|---|
| Cloud Computer | Environment |
| Install software script | Warm hook, run ahead of time so workspaces start with dependencies installed |
| Repository setup script | Start hook, run when a workspace starts |
| Environment variables and secrets | Environment variables, with sensitive values hidden after saving |
| Cloud workspace | Workspace: an isolated Linux VM with a desktop and Chrome |
| Claude Code, Codex, and Cursor agents | Claude Code, Codex, Cursor, Muse Code, OpenCode, and Pi |
| Routines | Automations with schedule, GitHub, GitLab, Slack, Linear, Sentry, or webhook triggers |
| Workspace link sharing | Workspace sharing within the organization |
| Conductor API | API, CLI, and MCP server |
| iOS app | iOS app |
Migrate from Conductor Cloud (docs)
The guide walks through each row of the table. It starts with a prompt you can paste into Claude Code, Codex, or Cursor on your laptop, so the agent reads your Conductor setup and recreates it with the Replicas CLI, and then lists the same steps for doing it by hand.
How to migrate from Conductor Cloud to Replicas (blog)
The blog post explains what to save before Conductor Cloud goes read-only, the reasoning behind each step, and what works differently in Replicas.
Decision guide
How to pick a Conductor Cloud alternative
Most teams are not choosing between good and bad tools. They are choosing between working models: an editor, a packaged autonomous engineer, a provider-native CLI, an open-source agent, or a shared cloud workspace. Decide which model fits how your team wants to delegate and review work, then compare products inside that model.
- You want a desktop app like local Conductor
- Paradev, or keep using the local Conductor app until it winds down in early 2027.
- You used one agent and want its vendor to host it
- Claude Code on the web, Codex cloud, or Cursor Cloud Agents.
- You want work to start from GitHub issues
- GitHub Copilot coding agent if the team already lives in GitHub.
- You want shared cloud workspaces with a choice of agents
- Replicas or Tembo, which run several agents in managed cloud environments.
Replicas fit
When Replicas is the right Conductor Cloud alternative
Replicas is strongest when the goal is delegated, reviewable engineering work in the cloud rather than a better local editing experience. Teams typically shortlist it when several of the following are true.
- Agents need to keep working after you close your laptop, in a cloud workspace your teammates can open.
- Your team uses more than one agent and wants to pick Claude Code, Codex, or Cursor per task with existing subscriptions or API keys.
- Different repositories or teams need different setups, which separate environments handle.
- Work should start from Slack, Linear, GitHub comments, schedules, or webhooks as well as the app.
- Some repositories are on GitLab.
Evaluation
Run the same five tasks through every finalist
Demos favor whichever product built the demo. Pick tasks from your own backlog and run them through each finalist with the same repository, the same review standard, and the same person judging the result.
- A code review follow-up: address reviewer comments on an open pull request and get CI green again.
- A CI failure: investigate a failing job, reproduce it, and ship a fix with the reasoning attached.
- A small feature from a ticket: implement it end to end, including tests, from a Linear or GitHub issue.
- A flaky end-to-end test: find the root cause instead of adding a retry.
- A backlog cleanup pass: remove dead code or stale feature flags across the repository without breaking anything.
FAQ