Skip to main content
Once Sazabi identifies the root cause of a production issue, choose Fix to send it to a Replicas agent. The agent works in your repository. Its progress, questions, and pull request appear in the Sazabi issue thread.

Connect Replicas to Sazabi

  1. In Replicas, give the GitHub integration access to the repository and add it to an environment.
  2. Ask a Replicas organization admin to create an organization key in Settings → API Keys.
  3. As a Sazabi organization admin, open Settings → Integrations, select Replicas, and choose Connect. Enter the key and check that your repository appears under Repositories.

Start a fix

Open the issue in Sazabi, choose Fix, and select Replicas if it is not already the project default. Confirm the repository and base branch if prompted, then choose Fix with Replicas. Follow the attempt in the issue thread. From an authenticated Sazabi CLI, set ISSUE_ID to the Sazabi issue ID and run:
Use the agent dispatch commands to reply to the agent or cancel the attempt. If the repository is missing or Replicas isn’t offered under Fix, see Sazabi’s setup and troubleshooting guide.

Query Sazabi from a Replicas workspace

To investigate logs and incidents from a workspace, add Sazabi from the environment’s suggested MCP servers, or install the native Sazabi plugin for SDK access. Sign in to Sazabi for the option you choose. Neither is required for the Fix handoff.