Replicas

The second major feature group is sandboxed environments, where each coding agent runs in an isolated virtual machine with its own development environment. The agent can install dependencies (e.g., npm install), spin up databases like Redis and Postgres, start dev servers on ports 3000 and 8000, and run tests to verify changes locally. This isolation ensures that code changes are tested in a reproducible environment that mirrors production, without affecting the main project until the PR is merged. It also prevents cross-contamination between tasks, so multiple agents can work simultaneously on different branches. The sandbox automatically sleeps when idle to save costs and can be woken on demand. This architecture provides a secure, scalable foundation for running autonomous coding agents, giving teams confidence that changes are thoroughly validated before review.

The third feature group is custom workflows via a REST API. Replicas exposes an endpoint at POST /v1/replica that allows teams to integrate coding agents into any automated pipeline. The payload includes the repository, a message describing the desired change, and the coding agent to use (e.g., "claude" or "codex"). This enables automation on top of Replicas, such as triggering code changes from CI/CD events, scheduled tasks, or external tools. Teams can build custom integrations that run code changes automatically in response to specific conditions, like fixing a recurring bug or updating configurations. This API gives developers complete flexibility to embed coding agents into their unique workflows, making Replicas a versatile tool for automating repetitive coding tasks at scale. It effectively acts as a programmable layer for background code changes.

The overall workflow follows a simple pattern: delegate, sandbox, pull request. First, a developer delegates a task using one of the supported integrations – Slack, Linear, GitHub, or the dashboard. Second, Replicas spins up a sandboxed virtual machine and assigns a coding agent (Claude Code or Codex) to work on the task. The agent reads the relevant files, implements the required changes, runs tests, and ensures everything works correctly. Third, the agent creates a pull request with a summary of the changes, including the diff and any relevant details. The developer reviews the PR, provides feedback if needed, and merges it when satisfied. This end-to-end automation streamlines the process from idea to merged code, reducing manual effort and enabling faster iteration. The entire workflow is designed to fit seamlessly into existing development practices.

Concrete use cases demonstrate the power of Replicas. A developer can mention @tryreplicas in a GitHub PR comment to request a bug fix, and within minutes a pull request with the fix is ready for review. On Slack, pinging @Replicas with a feature request like "add dark mode to settings" triggers the agent to implement the feature, run tests, and submit a PR. In Linear, assigning an issue such as "Implement notifications" causes Replicas to analyze the issue, read relevant source files, implement the feature, and create a PR with a detailed description. Teams using Replicas report shipping over 30% of their pull requests through these automated workflows. This significantly reduces manual coding effort, accelerates feature delivery, and allows engineers to focus on more critical work while routine changes are handled autonomously.

Replicas is designed for engineering teams and individual developers working with GitHub repositories and using tools like Slack, Linear, or project management platforms. It supports any GitHub repository the user has access to, and works with Claude Code and Codex as coding agents, with OpenCode support coming soon. Billing is credit-based: users subscribe or purchase credits, then spend them on active compute time. Workspaces automatically sleep when idle and wake on demand, so you pay only for actual usage. No code is stored in Replicas databases; each workspace is isolated, and only the user has SSH access. Sleeping workspaces are deleted after 7 days of inactivity for security. In summary, Replicas provides a secure, scalable, and cost-effective way to automate code changes using background coding agents, helping teams ship faster and reduce manual overhead.