Skip to main content

​
Supported capabilities

Core integration
  • Core integration: Capy — Connect Capy 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 Capy lets Sazabi hand an issue’s fix to Capy. You choose Fix on an issue, Capy works in your repository and opens a pull request, and Sazabi follows its progress in the issue thread. Capy is a coding agent integration: one of the agents listed under Settings > Integrations that Fix can hand off to.

​
Prerequisites

  • A Capy service user API key.
  • Organization admin access in Sazabi.
  • Repository access for Capy: Capy works only in repositories its GitHub App can reach. Connect GitHub at capy.ai > Settings > Integrations > GitHub, then add the repository to a Capy project.

​
Set up in the dashboard

1

​
Get your credentials

Create a Capy API key from Capy > Settings > API > Service users. The key starts with capy_.
2

​
Open the Capy integration

In the dashboard, go to Settings > Integrations and open Capy.
3

​
Connect with the key

Choose Connect and paste the key. Sazabi checks it with Capy before saving the connection.
4

​
Check repository access

The connection page’s Repositories section shows which repositories Fix can hand to Capy. 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 Capy, and choose Use this account. Fix then hands off to it without asking. For Capy, the connection page also lets you pick a Default environment for fixes.

​
Set up with the CLI

You can also connect Capy with the Sazabi CLI (installed and authenticated; see CLI reference). Capy 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:
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 Capy. Confirm the repository, and the base branch if asked, then choose Fix with Capy. Capy 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):
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 Capy. Confirm the attempt appears in the issue thread within a minute, and that sazabi agent-dispatches list --issue-id "$ISSUE_ID" lists it with Capy as the agent.

​
Troubleshooting

Capy did not accept this key - The key is wrong, revoked, or from the wrong account. Create a new one and reconnect. Capy can’t reach any repositories yet - Capy works only in repositories its GitHub App can reach. Connect GitHub at capy.ai > Settings > Integrations > GitHub, then add the repository to a Capy project. Fix doesn’t offer Capy - Confirm the connection shows connected under Settings > Integrations, and that the issue’s project has a repository Capy can reach.

​
Further reading

Issues

Open, investigate, and resolve issues.

Integrations

Browse the core integrations.