> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Replicas

> Connect Replicas so Sazabi can hand issue fixes to it and follow the result in the issue thread.

## Supported capabilities

MCP connectorCore integration

* **MCP connector**: [Replicas](https://docs.sazabi.com/catalogs/mcp-connectors/replicas.md) — Give the Sazabi agent tools to create and steer Replicas cloud coding-agent workspaces, chats, environments, and automations.
* **Core integration**: [Replicas](https://docs.sazabi.com/catalogs/integrations/replicas#core-integration) — Connect Replicas so Sazabi can hand issue fixes to it and follow the result in the issue thread.

Each connection method has its own setup and permissions. Connecting one method does not enable the others.

## Core integration

## About

Connecting Replicas lets Sazabi hand an issue's fix to Replicas. You choose **Fix** on an issue, Replicas works in your repository and opens a pull request, and Sazabi follows its progress in the issue thread. Replicas is a **coding agent** integration: one of the agents listed under [**Settings > Integrations**](https://app.sazabi.com/settings/integrations) that Fix can hand off to.

## Prerequisites

* A Replicas organization API key.
* Organization admin access in Sazabi.
* Repository access for Replicas: Replicas works only in repositories its GitHub integration can reach. Install GitHub at [app.replicas.dev > Integrations](https://app.replicas.dev/dashboard/integrations), then add each repository to a Replicas environment under **Environments**.

## Set up in the dashboard

**Step 1**

### Get your credentials

Create a Replicas **organization API key** from [Replicas settings](https://app.replicas.dev/dashboard/settings?tab=api-keys). The **Replicas organization ID** field is optional.

**Step 2**

### Open the Replicas integration

In the dashboard, go to [**Settings > Integrations**](https://app.sazabi.com/settings/integrations) and open **Replicas**.

**Step 3**

### Connect with the key

Choose **Connect** and paste the key. Sazabi checks it with Replicas before saving the connection.

**Step 4**

### Check repository access

The connection page's **Repositories** section shows which repositories Fix can hand to Replicas. **Default coding agent** is set per project, so it appears only when you open the connection from a project's settings: open the project, go to its **Integrations** settings, select Replicas, and choose **Use this account**. Fix then hands off to it without asking. For Replicas, the connection page also lets you pick a **Default environment** for fixes.

## Set up with the CLI

You can also connect Replicas with the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) (installed and authenticated; see [CLI reference](https://docs.sazabi.com/reference/cli/integrations.md)).

Replicas is an API-key provider, so pass its key as the `apiKey` credential. Read the key from an environment variable rather than pasting it inline:

```bash theme={"system"}
export REPLICAS_API_KEY=...   # your Replicas key
sazabi integrations connect replicas \
  --credentials "{\"apiKey\":\"$REPLICAS_API_KEY\"}"
```

Run `sazabi integrations list` to confirm the connection, or `sazabi integrations providers --json` to see each provider's credential fields.

## Fix issues

Open an issue in the project inbox, choose **Fix**, and pick Replicas. Confirm the repository, and the base branch if asked, then choose **Fix with Replicas**. Replicas works in the repository and opens a pull request; its progress, questions, and pull request appear in the issue thread.

From the CLI, hand the fix off and follow the attempt with `sazabi agent-dispatches` (see [CLI reference](https://docs.sazabi.com/reference/cli/agent-dispatches.md)):

```bash theme={"system"}
sazabi issues fix "$ISSUE_ID" --agent replicas
sazabi agent-dispatches list --issue-id "$ISSUE_ID"
```

`sazabi agent-dispatches reply` answers a question from the agent, and `sazabi agent-dispatches cancel` stops the attempt.

## Verify

Choose **Fix** on an open test issue and hand it to Replicas. Confirm the attempt appears in the issue thread within a minute, and that `sazabi agent-dispatches list --issue-id "$ISSUE_ID"` lists it with Replicas as the agent.

## Troubleshooting

**Replicas did not accept this key** - The key is wrong, revoked, or from the wrong account. Create a new one and reconnect.

**Replicas can't reach any repositories yet** - Replicas works only in repositories its GitHub integration can reach. Install GitHub at [app.replicas.dev > Integrations](https://app.replicas.dev/dashboard/integrations), then add each repository to a Replicas environment under **Environments**.

**Fix doesn't offer Replicas** - Confirm the connection shows connected under [**Settings > Integrations**](https://app.sazabi.com/settings/integrations), and that the issue's project has a repository Replicas can reach.

## Further reading

> [card] [Issues](https://docs.sazabi.com/detect/issues.md)
>
> Open, investigate, and resolve issues.

> [card] [Integrations](https://docs.sazabi.com/catalogs/integrations.md)
>
> Browse the core integrations.

> [card] [Replicas MCP connector](https://docs.sazabi.com/catalogs/mcp-connectors/replicas.md)
>
> Give the Sazabi agent Replicas tools over MCP.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.