For CTOs, VPs of Engineering and engineering leads

What is the right cloud coding agent for your team?

Answer ten questions about your team and get Replicas, Devin, Cursor, Claude Code, Codex and OpenCode ranked against your own criteria, with the reason behind every point.

Operated by Replicas, one of the platforms compared here. The criteria, the weights and every product's answers are published on How we score, and the chooser recommends another product when your answers point to one.

The eight things that decide it

Most cloud coding agents can write a decent pull request. Where they differ is which agents they run, where the work happens, how it starts, who pays for the model, and what your security team gets to see. These are the criteria the chooser scores.

Multi-harness support

Can you run Claude Code, Codex, Cursor and OpenCode, and switch when a better model ships?

Isolated cloud VMs

Does every task get its own machine, so agents can run services and tests and never share state?

Pull-request output

Does the agent open the PR, or hand you a branch to finish?

Starts where work is

Slack, Linear, GitHub and GitLab, plus schedules and webhooks.

Your own model keys

Does model spend land on your Anthropic, OpenAI, Bedrock or Foundry account, or a plan you already pay for?

Usage-based pricing

Per minute of compute, nothing while workspaces sleep, no seat fee.

Security and governance

SOC 2, SCIM, audit logs, HIPAA and self-hosting.

Parallel and scheduled runs

Many tasks at once, and work that starts with nobody in the room.

Our recommendation, and when it changes

Most teams

Replicas

For teams that hand work to agents and review pull requests, Replicas meets more of these criteria than anything else we compared: six agents to choose from, an isolated Linux VM per task, pull requests opened by the agent, starts from Slack, Linear, GitHub and GitLab, your own model plans or keys, and per-minute pricing with nothing charged while workspaces sleep.

Where it falls short: SOC 2 Type II is still in progress, Jira can't start a task, and agents run only in the cloud.

When your answers point elsewhere
  • Pairing in your editor all day: Cursor, or Claude Code and Codex in the terminal.
  • Jira triggers or SOC 2 Type II today: Devin or Cursor.
  • One agent, on GitHub, already on Claude or ChatGPT plans: Claude Code on the web or Codex cloud, included in the plan.
  • Open source end to end, on your own servers: OpenCode.
Find out which applies to you

At a glance

Checked against each vendor's published docs and pricing pages as of November 9, 2026. “Check” means we couldn't confirm it from public docs; ask the vendor.

CriterionReplicasDevinCursorClaude CodeCodexOpenCode
Agents
Multi-harness supportYesClaude Code, Codex, Cursor, OpenCode, Pi and Muse Code; pick the agent per taskNoDevin's own agent; you choose models inside it, not other agentsNoThe Cursor agent with a curated set of modelsNoClaude Code onlyNoCodex onlyNoOpenCode only, but with 75+ model providers
Environment
Isolated cloud VM per taskYesEach workspace is its own isolated Linux VM (2, 4 or 8 vCPU)YesEach session boots a fresh copy of the organization's snapshot in a Linux VMYesCloud Agents run in isolated VMs with full development environmentsYesClaude Code on the web runs each session in an Anthropic-managed Ubuntu VM (about 4 vCPU, 16 GB)YesCodex cloud runs tasks in OpenAI VMs (2 vCPU/8 GiB on Plus, 4 vCPU/16 GiB on Pro and Business)PartlyRuns wherever you put it; you provide and isolate the VM or container
Workflow
Pull request outputYesThe agent opens the pull request (GitHub) or merge request (GitLab)YesReturns pull requests for reviewYesCloud Agents push a branch and open pull requests with screenshots, videos and logsPartlyCloud sessions push a branch; you create the PR from the sessionPartlyYou open the PR from the finished taskPartly/oc comments through its GitHub integration; otherwise you script it
Local IDE workflowNoAgents run only in the cloud; the desktop app and CLI connect to cloud workspaces and can open one in VS CodeYesDevin Desktop and Devin CLIYesThe Cursor editor and CLIYesTerminal CLI and IDE extensions; --teleport pulls a cloud session into your terminalYesCLI, IDE extension and ChatGPT desktop appYesTerminal, desktop app and IDE integrations
Where work starts
Start from SlackYesMentions, DMs and threadsYesSlack and Microsoft TeamsYes@cursor in SlackCheckConfirm current Slack support with AnthropicCheckConfirm current Slack support with OpenAICheckNot part of the core tool; confirm or build it
Start from LinearYesAssign or mention on an issueYesListed as an integrationYes@cursor in LinearCheckConfirm with AnthropicCheckConfirm with OpenAICheckNot part of the core tool; confirm or build it
Start from GitLabYesIssues and merge requests; one workspace can span GitHub and GitLabYesGitLab and Bitbucket; self-managed GitLab on EnterprisePartlyWorks on GitLab repositories; @cursor comments are documented for GitHub and BitbucketPartlyGitLab repos can be sent as a bundle, but cloud sessions can't push backNoGitHub only for now; GitLab is on OpenAI's roadmapCheckConfirm with the OpenCode project
Models and billing
Bring your own model keysYesAnthropic, OpenAI, AWS Bedrock, Microsoft Foundry, OpenRouter, Cursor and OpenAI-compatible keysPartlyA ChatGPT plan can pay for GPT usage; no API-key option is documentedNoCloud Agents bill your Cursor plan's usage at model ratesPartlyCloud sessions need a Claude plan; API keys and Bedrock aren't supported there (the CLI takes them)PartlyCodex cloud requires a ChatGPT sign-in; API keys work only in the CLIYes75+ providers through your own keys, plus local models
Usage-based compute pricingYesBilled per workspace minute by VM size; sleeping and archived workspaces cost nothing; seats are freePartlyUsage quota plus credits; Teams adds $40 per seatPartlyPlan usage at model rates; Cloud Agents need a Premium, Teams or Enterprise planNoSeat-based plans from $20/mo; no separate VM chargeNoSeat-based ChatGPT plans from $20/moPartlyThe software is free; your servers cost whatever you pay for them, idle or not
Security and governance
SOC 2 Type II todayNoSOC 2 Type II is in progressYesSOC 2 Type II since September 2024YesSOC 2 Type II attestationCheckCheck Anthropic's Trust CenterCheckCheck OpenAI's Trust PortalPartlyCompliance is your infrastructure's
SCIM provisioningYesSCIM provisioning on EnterpriseCheckSAML and OIDC SSO on Enterprise; confirm SCIM with CognitionYesSSO and SCIMCheckCheck the Claude Enterprise planCheckCheck the ChatGPT Enterprise planNoNo hosted user management
Self-hosted or dedicated deploymentYesSelf-hosted or dedicated single-tenant deployment on EnterprisePartlyA dedicated VPC run by Cognition; Outposts move command execution to your machinesPartlySelf-hosted machines for tool execution; the service itself is Cursor-hostedPartlyCloud sessions are Anthropic-hosted; the CLI can run on servers you controlPartlyCodex cloud is OpenAI-hosted; the Apache-2.0 CLI runs anywhereYesRuns entirely on your own machines

See all 6 products on every criterion

Get a second opinion on your shortlist

Tell us what you're weighing and an engineer from the Replicas team, who operate this site, will reply by email. We'll point you to whichever option fits, including when that isn't Replicas.