Replicas

Replicas runs coding agents in cloud workspaces built from an environment — a config bundle that carries the repository binding plus the variables, files, skills and MCPs the agent gets. The Cargo integration lets a workflow launch an agent and use whatever it produced (branches, pull requests) in downstream nodes.

​

Authentication

Connect to Replicas using an API key created from the Replicas dashboard under Organization → Settings → API Keys.

​

Connection details

---

​

Replicas actions

​

Launch agent

Create a workspace and send an initial message to a coding agent. Configuration The Environment dropdown lists the team and personal environments in your Replicas organization. The Global environment is not listed: it only layers configuration onto the other environments and has no repository binding, so it cannot back a workspace. Leave Workspace name empty to get a name derived from the workflow node and the record being processed. Waiting for the agent The node stays pending until Replicas calls back, so downstream nodes run against a finished agent rather than a workspace that has only just started. Replicas notifies Cargo directly — nothing is polled — and the node resumes on the replica.turn_completed callback. A replica.error callback fails the node with the reason Replicas reported. Output

---

​

Use cases

---

​

Best practices

1. Give the agent a complete prompt - It cannot ask follow-up questions mid-run
2. Pick the environment carefully - It decides which repository the agent works on
3. Use plan mode to review first - Have the agent propose an approach before it writes code
4. Sleep or archive when done - Workspaces bill per minute while they stay up