# Replicas

> The background coding agent. Delegate tasks to coding agents that work in sandboxed development environments. Backed by Y Combinator.

- Home: https://replicas.dev/
- Docs: https://docs.replicas.dev
- Pricing: https://replicas.dev/pricing
- Enterprise: https://replicas.dev/enterprise
- Blog: https://replicas.dev/blog
- Resources: https://replicas.dev/resources
- Coding agent alternatives: https://replicas.dev/alternatives
- Replicas vs Devin: https://replicas.dev/replicas-vs-devin
- Replicas vs Cursor: https://replicas.dev/replicas-vs-cursor
- Replicas vs Claude Code: https://replicas.dev/replicas-vs-claude-code
- Cloud coding agents: https://replicas.dev/cloud-coding-agents
- Background coding agents: https://replicas.dev/background-coding-agents
- AI coding agents: https://replicas.dev/ai-coding-agents
- Best cloud coding agents: https://replicas.dev/best-cloud-coding-agents
- AI code review agent: https://replicas.dev/use-cases/ai-code-review-agent
- Automated code review: https://replicas.dev/use-cases/automated-code-review
- Automated code operations: https://replicas.dev/automated-code-operations-cloud-coding-agents
- Best AI coding tools in 2026: https://replicas.dev/best-ai-coding-tools-2026
- Code review follow-up: https://replicas.dev/use-cases/code-review-follow-up
- Linear issue to PR: https://replicas.dev/use-cases/linear-issue-to-pr
- Slack to coding agent: https://replicas.dev/use-cases/slack-to-coding-agent
- Backlog cleanup: https://replicas.dev/use-cases/backlog-cleanup
- Automated bug fixes: https://replicas.dev/use-cases/automated-bug-fixes
- PostHog AI product engineer: https://replicas.dev/use-cases/posthog-ai-product-engineer
- Get started: https://replicas.dev/auth
- Auth notes: https://replicas.dev/auth.md
- Book a demo: https://cal.com/connor-replicas/30min
- Contact: founders@replicas.dev

## How it works

- **Assign from anywhere:** From Linear, Slack, GitHub, GitLab, or the dashboard. No new workflow.
- **Work with any harness:** Claude Code, Codex, Cursor, or Opencode — each in its own Linux VM.
- **Review what comes back:** A pull request, a reply, a recording. Merge it, comment on it, or send it again.

## Integrations

Start agents wherever work shows up.

- **Dashboard:** Chat directly from the web for full control. Watch the diff, steer the plan, and pair with the agent when you want to.
- **Slack:** Ping Replicas from any channel to start work instantly. No context switching, just agents running where your team already talks.
- **Linear:** Turn issues into active agent runs. Replicas reads the ticket, gathers context, and starts implementation without another handoff.
- **GitHub & GitLab:** Tag Replicas inside a comment or pull request. The agent investigates the codebase, tests a fix, and comes back with changes ready to review.
- **Automations & API:** Fire a run from a schedule, a webhook, or one API call. Replicas provisions the workspace and reports back with nobody in the room.

```
POST /v1/replica
{
  "repository": "acme/app",
  "message": "Add dark mode",
  "coding_agent": "claude"
}
```

## Analytics

Every minute is attributable — to a source, a person, a harness, a model, the credential that paid for it, and the skills and MCP servers the agent reached for.

## Sandboxed environments

Each task runs in an isolated Linux VM you configure once: warm hooks preinstall dependencies and images before a machine is claimed, MCPs, skills, files, and variables come with it, and agents drive a real desktop and browser to verify their own work.

## Customers

Engineering teams hand code review, recurring maintenance, and feature work to agents running in the cloud, then measure exactly what shipped.

### Parrot: How Parrot reviews every pull request with a team of cloud agents

> I think Replicas makes it super easy to spin up Claude coding agents and switch between different harnesses, which is very important to stay with the latest models. You get to use your same coding agents that you use normally, like Codex and Cursor and Claude, in the cloud, in a harness you’re very familiar with. Developer machines and cloud machines basically have the same environment now.
>
> — Erik Dahl, Co-founder & CTO, Parrot

- **23.5k** automated cloud-agent jobs in July
- **270k+** minutes running coding agents in July

Read the story: https://replicas.dev/customers/parrot

### Moda: How Moda moved its entire engineering team from local IDEs to cloud agents

> Going from local to cloud coding agents was arguably as big of a jump as using coding agents in the first place.
>
> — Pranav Bedi, CEO, Moda

- **4.7k** cloud-agent jobs in July
- **500k+** minutes running coding agents in July
- **~2k** jobs launched by automations in July
- **100%** of the engineering team using Replicas over other IDEs

Read the story: https://replicas.dev/customers/moda

### Knowunity: How Knowunity doubled engineering velocity with cloud agents

> Replicas completely changed the way we run engineering at Knowunity by allowing engineers to trigger cloud agents from anywhere, like Slack, Linear, or with automations.
>
> — Lucas Hild, CTO, Knowunity

- **2.8k** cloud agents launched in July
- **50%** of pull requests produced by cloud agents
- **2×** engineering velocity
- **2/3** less time spent fixing bugs

Read the story: https://replicas.dev/customers/knowunity

All customer stories: https://replicas.dev/customers

Engineering teams use Replicas to ship over 30% of pull requests, including:

- [Mintlify](https://mintlify.com)
- [Knowunity](https://knowunity.com)
- [Composio](https://composio.dev)
- [Moda](https://moda.dev)
- [Dart](https://dartai.com/)
- [Chronicle Labs](https://chronicle-labs.com)
- [Sorce](https://sorce.jobs)
- [Taiga](https://taigabilling.com)
- [Trellis](https://www.trellistech.com/)
- [Hyperspell](https://www.hyperspell.com)
- [Totalis](https://totalis.trade)
- [Parrot](https://www.parrotapp.com)

## FAQ

### Which coding agents can I run?
Claude Code, Codex, Opencode, and Cursor. Every agent runs on the same environment primitives, so you can mix agents across tasks or run several inside one workspace.

### What does an agent's environment look like?
Each agent works in an isolated cloud environment with your repository, tools, dependencies, and services ready to use.

### Is the output always a pull request?
No. Agents can return a pull request, commit, comment, or completed task for you to review, merge, or send back.

### What repositories can I use?
Any GitHub or GitLab repository you have access to. Connect your GitHub or GitLab account and select which repos to enable.

### How does billing work?
Usage is measured in minutes of workspace runtime. Every plan includes a monthly allowance of minutes, and you pay only for active compute time. Workspaces automatically sleep when idle and wake on demand.