Integrating Sazabi with Cursor

Learn how to connect Sazabi to Cursor so Chat can launch Cursor Cloud Agents to automatically fix code issues and create pull requests.

About the Sazabi integration for Cursor

The Sazabi integration for Cursor enables automated code fixes. When Chat identifies a bug during investigation, it can launch a Cursor Cloud Agent to implement the fix and open a pull request.

With the Sazabi integration for Cursor, you can:

• Ask the assistant to fix bugs it identifies during investigation.
• Automatically create pull requests with fixes.
• Get code changes reviewed by your team through your normal PR workflow.
• Track fix progress directly in your Sazabi conversation.

Prerequisites

Before you connect Cursor, make sure you have:

• A Sazabi account. Request access at sazabi.com
• A Cursor account with Cloud Agent access. Cloud Agents require a Cursor Pro or Business subscription.
• The GitHub integration configured, so pull requests can be created.

Installation

Launching a Cursor agent

Once connected, you can ask the assistant to fix issues directly in your conversations:

Fix this bug and create a PR.

The assistant will analyze the issue, determine what code changes are needed, and launch a Cursor Cloud Agent to implement the fix.

What happens when you launch an agent

Example workflows

Fixing a null pointer exception

User: We are seeing null pointer exceptions in the checkout flow.
      Can you investigate and fix it?

Assistant: I found the issue. There's a missing null check in the
            cart validation logic. I'll launch a Cursor agent to fix it.

[Cursor agent creates PR #123 "Fix null check in cart validation"]

Adding input validation

User: The user registration form is accepting invalid email addresses.
      Can you add proper validation?

Assistant: I'll add email validation to the registration form. Launching
            a Cursor agent now.

[Cursor agent creates PR #124 "Add email validation to registration form"]

Refactoring error handling

User: The payment service is swallowing errors and returning generic
      messages. Can you refactor it to handle errors properly?

Assistant: I'll refactor the error handling to propagate specific error
            types and messages. Launching a Cursor agent.

[Cursor agent creates PR #125 "Improve error handling in payment service"]

Troubleshooting

Agent failed to complete

If a Cursor agent fails to complete:

1. Check your Cursor subscription status. Cloud Agents require an active Pro or Business subscription.
2. Verify the target repository is accessible and has no branch protection rules blocking new branches.
3. Check the Cursor dashboard for agent logs and error details.

No pull request created

If the agent completes but no PR appears:

1. Verify the GitHub integration has access to the target repository.
2. Check that the repository allows PR creation from new branches.
3. Look for the branch in GitHub; the agent may have created the branch but failed to open the PR.

Wrong repository

If the agent is making changes to the wrong repository:

1. Go to Settings > Integrations > Cursor.
2. Update the target repository setting.
3. Make sure the correct repository is also connected via the GitHub integration.

Security considerations

• Cursor agents run in Cursor's cloud infrastructure, not your local machine.
• All code changes go through your normal PR review process.
• The agent can only access repositories you have explicitly granted access to.
• You can revoke Cursor access at any time from the Sazabi dashboard.