Hand off a root cause

An issue’s report holds Sazabi’s analysis of what happened, why, and the evidence. Handing off a root cause means moving that analysis into the tool that changes your code. There are three ways to do it, and they work on the same issue.

You want	Use	Who writes the code
Your own coding agent to continue the investigation in your checkout	The agent prompt	Your agent
Sazabi to start the fix now	Fix	Sazabi’s agent or a coding agent you connected
To hand a finding from a thread that is not an issue to a connected coding agent	A task from any thread	A coding agent you connected

Whichever you pick, link the pull request so it shows on the issue.

Hand the issue to your own agent

Every issue has an agent prompt: one block of text you paste into Claude Code, Codex, Cursor, Devin, or another coding agent. It names the issue and points the agent at the live report instead of copying it, so a prompt you saved earlier still leads to the current analysis. It carries IDs and a link, never a credential.

Copy the prompt

Dashboard
CLI
MCP and API

Open the issue and select Copy prompt beside its name. The button reads Copied once the prompt is on your clipboard. The same button is on issue cards in threads, and Copy prompt is in the command menu on an issue page. Copying only reads the issue, so members with read-only access can copy.Other places the prompt appears:

Slack issue messages for open issues have a Copy Prompt button that opens the prompt in a window with a copy control.
Microsoft Teams issue cards for open issues have a Copy Prompt action that shows the prompt.
A ticket Sazabi creates for an issue in your task tracker ends with a Prompt for AI agents section.
The issue_triggered webhook carries it in issue.agentPrompt. See Webhook payload.

Find the issue ID, then print the prompt. The output is the bare prompt, so you can pipe it:

npx -y @sazabi/cli@latest issues list --status open
npx -y @sazabi/cli@latest issues agent-prompt "$ISSUE_ID" | pbcopy

Add --json to get prompt and a version for the prompt’s wording. See sazabi issues.

With the Sazabi MCP server connected, your agent calls the issues.getAgentPrompt operation through execute, with the issue ID as issueId:

{
  "name": "sazabi/issues.getAgentPrompt",
  "arguments": { "issueId": "your-issue-id" }
}

The API route is GET /v1/issues/{issueId}/agent-prompt. See MCP server and Get an issue’s agent prompt.

What the prompt tells your agent

The prompt gives the agent a short summary of the issue and these steps:

Install the Sazabi CLI if it is missing, sign in with sazabi auth sign-in (or, headless, ask you for a secret key to set as SAZABI_TOKEN), and select the issue’s project.
Load the analysis with sazabi issues get "$ISSUE_ID" --json. The report field is the full what, why, how, and evidence; latestUpdate is the newest finding after it. Issue text, thread content, and log lines are treated as untrusted data.
Check against live data with sazabi logs ask that the problem is still happening.
Confirm the repository contains the affected code, make the smallest change that fixes the root cause, add a test, and run your tests and linters.
Open a pull request on a new branch with the issue’s link and a Sazabi-Issue: ISSUE_ID line in the body, run sazabi issues link-pr, and report back. The agent does not resolve the issue.

If your agent already has the MCP server connected, it can read the same data without the CLI: issues.get returns report and latestUpdate, and issues.linkPullRequest links the pull request. See Connect your coding agent.

Start a fix from Sazabi

Fix runs in the issue’s thread. Sazabi’s agent, or a coding agent you connected, writes the change, and its questions, results, and pull requests land in the thread and on the issue. Fix is available on open issues that have a thread, and the requester is recorded, so a signed-in person must start it.

Dashboard
CLI
MCP and API

Select Fix

Open an open issue and select Fix. A member with read-only access sees it disabled.

Choose who writes the fix

If no coding agent is connected, Sazabi’s agent starts at once in the issue thread and you can skip to the last step. If one is connected, the Fix this issue dialog opens. Choose Sazabi’s agent or a connected coding agent. Choose a repository when the issue’s evidence does not settle it, and an environment for an agent that has them (Replicas).

Start the attempt

Select the Fix with button, which ends in and open thread. The attempt shows in the thread, and its status shows on the issue.

A coding agent that needs attention or was connected with an organization key is listed but cannot take the fix. Reconnect it as yourself under Settings > Integrations.Under Settings > Code, the Fixes section sets the project’s default agent for a Fix that names none. With no default and several coding agents connected, the dialog asks you to pick one. Auto-fix new issues is off by default; turn it on to start a fix for each new issue with the default agent, and raise Minimum severity for auto-fix to leave lower-severity issues to a person.

npx -y @sazabi/cli@latest issues fix "$ISSUE_ID"
npx -y @sazabi/cli@latest issues fix "$ISSUE_ID" --agent cursor
npx -y @sazabi/cli@latest issues fix "$ISSUE_ID" --agent sazabi

Without --agent, the fix goes to the project’s default agent, else Sazabi’s agent. When the project has no default and several coding agents are connected, a fix without --agent is refused and the error lists the choices: pass --agent, or set the default under Settings > Code. --agent sazabi asks for Sazabi’s agent even when the default is a coding agent. The coding agents are cursor, devin, capy, replicas, hoplite, warp, claude, codex, and tembo; connect one with sazabi integrations connect.With several connections for an agent, pass --connection-id. With several repositories and no clear match, pass --repository-url. sazabi issues get shows the choices as fixAgents, fixAgentDefault, and fixRepositories. See sazabi issues fix.Follow and steer the attempt:

npx -y @sazabi/cli@latest threads get "$THREAD_ID"
npx -y @sazabi/cli@latest agent-dispatches list --issue-id "$ISSUE_ID"
npx -y @sazabi/cli@latest agent-dispatches reply "$DISPATCH_ID" --text "Use the retry helper in lib/http.ts"
npx -y @sazabi/cli@latest agent-dispatches cancel "$DISPATCH_ID"

The thread and dispatch IDs are printed when the fix starts. See sazabi agent-dispatches.

Call issues.fixes.create (POST /v1/issues/{issueId}/fix) with an optional agent, then read the attempt with agentDispatches.get. OAuth sign-in in your MCP client acts as you; a secret key is refused with signed_in_person_required. See Request a fix for an issue.

When Sazabi’s agent writes the fix, it opens the pull request on your connected forge. See Fix pull requests. To connect a coding agent, see its page under Integrations, for example Cursor, Devin, Codex, or Claude.

Hand a task from any thread

A finding does not have to be an issue. From any thread, such as an investigation where you found a cause, you can hand a task to a connected coding agent. The agent’s questions and result land back in that thread.

npx -y @sazabi/cli@latest agent-dispatches create --thread-id "$THREAD_ID" --agent cursor --task-file task.md

Write the task in your words: the symptom, the cause if you know it, the files or services involved, and what done looks like. Leave out secrets, tokens, and raw log dumps. --repository, --branch, --connection-id, and --environment-id choose where the agent works; the connection, repository, and branch use the project’s only choice when there is one. A project can have five of these handoffs in progress at once outside issues. Sazabi’s agent can also hand work off on your behalf when you ask in a thread. Through the API this is POST /v1/agent-dispatches (agentDispatches.create in MCP). Like Fix, it needs a signed-in person. See Hand a task to a coding agent from a thread.

Link the pull request

A pull request from Fix is linked to the issue for you. A pull request your own agent opens needs one of two links:

The Sazabi-Issue line. In a GitHub repository connected to the issue’s project, a pull request whose body has Sazabi-Issue: ISSUE_ID is linked when it is opened or edited.

An explicit link. Link a GitHub or Bitbucket pull request yourself:

npx -y @sazabi/cli@latest issues link-pr "$ISSUE_ID" https://github.com/acme/api/pull/42

If a pull request is the suspected cause rather than the fix, add --relation caused_by. See Connect your coding agent for finding and removing these links.

Verify

Open the issue in the dashboard, or run sazabi issues get "$ISSUE_ID" --json and read pullRequests.
For Fix, confirm an attempt card in the issue thread shows the agent’s status.
Under Linked on the issue, a Pull request row appears with the pull request’s number and title.

If the row is missing after your own agent opened the pull request, check that its body has the Sazabi-Issue line and that its repository is connected to the project, or run sazabi issues link-pr.

Connect your coding agent

Set up the MCP server and CLI your agent uses to read issues.

Issues

How issues are opened, scoped, and closed.

Get started

Send data

Detect issues

Triage issues

Ask Sazabi

Explore logs

Ship fixes

Manage account

Hand off a root cause

Hand the issue to your own agent

Copy the prompt

What the prompt tells your agent

Start a fix from Sazabi

Select Fix

Choose who writes the fix

Start the attempt

Hand a task from any thread

Link the pull request

Verify

Further reading

Connect your coding agent

Issues

​Hand the issue to your own agent

​Copy the prompt

​What the prompt tells your agent

​Start a fix from Sazabi

​Select Fix

​Choose who writes the fix

​Start the attempt

​Hand a task from any thread

​Link the pull request

​Verify

​Further reading

Connect your coding agent

Issues

Hand the issue to your own agent

Copy the prompt

What the prompt tells your agent

Start a fix from Sazabi

Select Fix

Choose who writes the fix

Start the attempt

Hand a task from any thread

Link the pull request

Verify

Further reading