sazabi issues

sazabi issues — Manage issues. Subcommands: create, list, search, get, fix, read, unread, agent-prompt, link-pr, link-task, create-task, unlink-pr, reject, resolve, ignore, reopen, mute, unmute, update.

`sazabi issues`

Manage issues

sazabi issues <subcommand>

sazabi issues create --from-json issue.json  # Create an issue
sazabi issues list  # List all issues
sazabi issues search checkout  # Search issues
sazabi issues get <issue-id>  # Get one issue
sazabi issues fix <issue-id>  # Ask Sazabi to fix an issue
sazabi issues read <issue-id>  # Mark an issue read for you
sazabi issues unread <issue-id>  # Mark an issue unread for you
sazabi issues agent-prompt <issue-id>  # Print the agent prompt
sazabi issues link-pr <issue-id> <pr-url> --relation caused_by  # Link a suspected cause
sazabi issues unlink-pr <issue-id> <pr-url> --relation caused_by  # Remove a suspected cause
sazabi issues link-task <issue-id> ENG-123  # Link an existing tracker task
sazabi issues reject <issue-id> --reason not_real  # Reject an issue
sazabi issues resolve <issue-id>  # Resolve an issue
sazabi issues ignore <issue-id>  # Ignore an issue
sazabi issues mute <issue-id>  # Mute an issue
sazabi issues unmute <issue-id>  # Unmute an issue
sazabi issues update <issue-id> --severity high --note "..."  # Change severity

`sazabi issues create`

Create an issue, reusing an existing open issue when one matches

sazabi issues create [options]

Flag	Type	Required	Description
`--token`	string	No	Override token (prefer SAZABI_TOKEN; arguments are visible to other local users)
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON
`--name`	string	No	Stable issue name: at most 80 characters, plain English, “<service or surface>: <customer-visible symptom>”, no counts, timestamps, or internal identifiers
`--content-mdx`	string	No	One message for the customer’s engineer, posted to Slack as written. No headings. Brief, natural language without emojis or em dashes. State the observed problem, affected scope and material uncertainty. Keep measured populations and time windows. Add a next action only when it adds a concrete lead; omit generic inspect/check handoffs. At most 120 words outside code and 3000 characters after Slack formatting. No line may start with a section label such as Summary:. No Sazabi identifiers.
`--severity`	string	No	Issue severity, by impact. critical: Happening now in production: an outage of the service, of a flow most users depend on, or of a whole feature; or data loss, a security exposure, or failed payments. high: Happening now in production: at least 1% of attempts failing or a region down; or production data loss, exposure, or failed payments that has stopped. medium: A failure limited to a few users or one path, a broad internal failure, a production outage that ended on its own, or serious harm outside production. low: No user or system impact, a transient blip, an internal failure on one item or a rare path, or other work outside production, including eval, training, and canary runs. Omitted, the issue is stored as medium.
`--component`	string	No	Required component ID. List with `sazabi components list` (available once the Components page is enabled for your organization); register one if none fits
`--from-json`	string	No	Read issue fields from a JSON file, or ’-’ for stdin

sazabi issues create --content-mdx "Checkout is returning 500s due to pool exhaustion." --component "$COMPONENT_ID"  # Create an issue from MDX content
sazabi issues create --from-json issue.json  # Create an issue from a JSON file with contentMdx
cat issue.json | sazabi issues create --from-json - --json  # Create an issue from stdin

`sazabi issues list`

List issues in the active project

sazabi issues list [options]

Flag	Type	Required	Description
`--token`	string	No	Override token (prefer SAZABI_TOKEN; arguments are visible to other local users)
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON
`--status`	string	No	Filter by status: open, resolved, or ignored
`--severity`	string	No	Filter by severity: low, medium, high, or critical
`--type`	string	No	Filter by type: reliability, correctness, security, efficiency
`--category`	string	No	Filter by category, such as active_attack or outage
`--component`	string	No	Filter by component ID
`--caused-by`	string	No	Filter by suspected-cause pull request URL
`--limit`	string	No	Maximum number of issues to return (default: 50, max: 100)
`--cursor`	string	No	Pagination cursor from previous response

sazabi issues list  # List all issues
sazabi issues list --status open  # List open issues only
sazabi issues list --component <component-id>  # List issues for a component

`sazabi issues search`

Search issues by text and filters

sazabi issues search [text...] [options]

Flag	Type	Required	Description
`--token`	string	No	Override token (prefer SAZABI_TOKEN; arguments are visible to other local users)
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON
`--status`	string	No	Filter by status: open, resolved, or ignored
`--severity`	string	No	Filter by severity: low, medium, high, or critical
`--type`	string	No	Filter by type: reliability, correctness, security, efficiency
`--category`	string	No	Filter by category, such as active_attack or outage
`--component`	string	No	Filter by component ID
`--caused-by`	string	No	Filter by suspected-cause pull request URL
`--limit`	string	No	Maximum number of issues to return (default: 50, max: 100)
`--cursor`	string	No	Pagination cursor from previous response
`--include-delivery-metadata`	boolean	No	Include delivery metadata in JSON output

sazabi issues search checkout timeout --status open  # Best matches in open issues' names and descriptions
sazabi issues search --severity critical --json  # No text: newest critical issues

`sazabi issues get`

Get one issue by ID

sazabi issues get <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token (prefer SAZABI_TOKEN; arguments are visible to other local users)
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON

sazabi issues get <issue-id>  # Get one issue

`sazabi issues fix`

Fix an open issue with Sazabi’s agent or a coding agent Needs a signed-in person (sazabi auth sign-in): a fix records who asked for it, so an organization secret key is refused with that reason, not as invalid. Coding agents: cursor (Cursor), devin (Devin), capy (Capy), replicas (Replicas), hoplite (Hoplite), warp (Warp Oz), claude (Claude Agent), codex (Codex), tembo (Tembo); connect one with sazabi integrations connect <agent>. Without —agent, the fix goes to the project’s default agent (sazabi issues get shows a coding agent default as fixAgentDefault), or to Sazabi’s own agent in the issue thread when the project has none. Only a person chooses the default, in Settings > Code in the dashboard, with Make default on the agent’s connection page, or in the dashboard’s Fix dialog, which asks for it when the project has none; a handoff never sets or changes it. When the project has no default and several coding agents are connected, a fix without —agent is refused: pass —agent or choose the default first. With —agent, the fix is handed to the connected account of that coding agent and runs in the same thread: its questions, results, and pull requests land there and on the issue; —agent sazabi asks for Sazabi’s own agent even when the default is a coding agent. The organization’s one connected account for the agent is used; with several, pass —connection-id. The repository is the one the issue’s evidence points at (its pull requests, earlier attempts, the report), else the project’s one connected GitHub repository; pass —repository-url only when several are connected and the evidence does not settle it (sazabi issues get shows fixRepository). Replicas runs in an organization environment: pass —environment-id to choose one that holds the repository (the API’s integrations.codingAgentEnvironments.list reads the connection’s environments); omitted, the project’s remembered environment is used while it still holds the repository, else Replicas picks. Follow the attempt with sazabi agent-dispatches get.

sazabi issues fix <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token (prefer SAZABI_TOKEN; arguments are visible to other local users)
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON
`--agent`	string	No	Who fixes it: a connected coding agent (cursor, devin, capy, replicas, hoplite, warp, claude, codex, tembo), or sazabi for Sazabi’s own agent even when the project’s default is a coding agent
`--connection-id`	string	No	With —agent: the connected account to use; needed when the organization has several for the agent (see sazabi integrations list)
`--repository-url`	string	No	With —agent: the project repository to work in, https://github.com/<owner>/<repo>; for a coding agent needed only when several are connected and the issue’s evidence does not point at one, for sazabi the repository its run works in and opens the pull request against
`--base-branch`	string	No	With —agent: the branch to start from; defaults to the repository’s base branch in the project, then its default branch on GitHub
`--environment-id`	string	No	With —agent replicas: the id of the Replicas organization environment to run in, one that holds the repository (the API’s integrations.codingAgentEnvironments.list reads them); omitted, the project’s remembered environment, else Replicas’s own pick
`--client-request-id`	string	No	Stable request ID for a coding-agent handoff; reuse only when retrying the same request

sazabi issues fix <issue-id>  # Request a fix from the project's default agent, else Sazabi's; follow it in the issue thread
sazabi issues fix <issue-id> --agent <agent>  # Hand the fix to a connected coding agent: cursor, devin, capy, replicas, hoplite, warp, claude, codex, tembo
sazabi issues fix <issue-id> --agent sazabi  # Sazabi's own agent, even when the default is a coding agent
sazabi issues fix <issue-id> --agent <agent> --connection-id <connection-id>  # When the organization has several connections for the agent
sazabi issues fix <issue-id> --agent <agent> --repository-url https://github.com/<owner>/<repo>
sazabi issues fix <issue-id> --agent replicas --environment-id <environment-id>  # Run in that Replicas environment

`sazabi issues read`

Mark an issue read for you, up to its latest activity

sazabi issues read <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token (prefer SAZABI_TOKEN; arguments are visible to other local users)
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON

sazabi issues read <issue-id>  # Clear the issue's unread marker for you

`sazabi issues unread`

Mark an issue unread for you

sazabi issues unread <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token (prefer SAZABI_TOKEN; arguments are visible to other local users)
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON

sazabi issues unread <issue-id>  # Bring the issue back as unread for you

`sazabi issues agent-prompt`

Print the prompt that hands an issue to your coding agent

sazabi issues agent-prompt <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token (prefer SAZABI_TOKEN; arguments are visible to other local users)
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON

sazabi issues agent-prompt <issue-id>  # Print the prompt
sazabi issues agent-prompt <issue-id> | pbcopy  # Copy it on macOS

`sazabi issues link-pr`

Link a pull request to an issue

sazabi issues link-pr <issue-id> <pr-url> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token (prefer SAZABI_TOKEN; arguments are visible to other local users)
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON
`--relation`	string	No	Relationship: fixes (default) or caused_by

sazabi issues link-pr <issue-id> https://github.com/acme/api/pull/42 --relation caused_by

`sazabi issues link-task`

Link an existing Linear, Jira, or GitHub task to an issue

sazabi issues link-task <issue-id> <task> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token (prefer SAZABI_TOKEN; arguments are visible to other local users)
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON

sazabi issues link-task <issue-id> ENG-123
sazabi issues link-task <issue-id> https://linear.app/acme/issue/ENG-123

`sazabi issues create-task`

Create a Linear ticket for an issue and link it Files the ticket in the Linear team the project files into (its Linear task creation rule, else the Linear integration’s team), carrying the issue’s brief for a coding agent and a link back to the issue. An issue that already has a task gets that task back.

sazabi issues create-task <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token (prefer SAZABI_TOKEN; arguments are visible to other local users)
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON

sazabi issues create-task <issue-id>

`sazabi issues unlink-pr`

Remove a pull request relationship from an issue

sazabi issues unlink-pr <issue-id> <pr-url> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token (prefer SAZABI_TOKEN; arguments are visible to other local users)
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON
`--relation`	string	No	Required relationship: fixes or caused_by

sazabi issues unlink-pr <issue-id> https://github.com/acme/api/pull/42 --relation caused_by

`sazabi issues reject`

Permanently reject an issue

sazabi issues reject <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token (prefer SAZABI_TOKEN; arguments are visible to other local users)
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON
`--reason`	string	No	Required: not_real, duplicate, incorrect_details, or something_else

sazabi issues reject <issue-id> --reason not_real  # Reject an issue that isn’t real

`sazabi issues resolve`

Resolve an open issue

sazabi issues resolve <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token (prefer SAZABI_TOKEN; arguments are visible to other local users)
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON

sazabi issues resolve <issue-id>  # Resolve an issue

`sazabi issues ignore`

Ignore an issue

sazabi issues ignore <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token (prefer SAZABI_TOKEN; arguments are visible to other local users)
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON

sazabi issues ignore <issue-id>  # Ignore an issue

`sazabi issues reopen`

Reopen a resolved or ignored issue

sazabi issues reopen <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token (prefer SAZABI_TOKEN; arguments are visible to other local users)
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON
`--note`	string	No	What came back, up to 2000 characters. Posted with the reopen announcement and shown in the issue’s history.

sazabi issues reopen <issue-id>  # Reopen a resolved or ignored issue
sazabi issues reopen <issue-id> --note "POST /checkout returns 502 again: 42 errors since 14:02 UTC"  # Reopen with what came back

`sazabi issues mute`

Mute an issue

sazabi issues mute <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token (prefer SAZABI_TOKEN; arguments are visible to other local users)
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON

sazabi issues mute <issue-id>  # Mute an issue

`sazabi issues unmute`

Unmute an issue

sazabi issues unmute <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token (prefer SAZABI_TOKEN; arguments are visible to other local users)
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON

sazabi issues unmute <issue-id>  # Unmute an issue

`sazabi issues update`

Change an issue’s severity, types or categories

sazabi issues update <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token (prefer SAZABI_TOKEN; arguments are visible to other local users)
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON
`--severity`	string	No	Issue severity, by impact. critical: Happening now in production: an outage of the service, of a flow most users depend on, or of a whole feature; or data loss, a security exposure, or failed payments. high: Happening now in production: at least 1% of attempts failing or a region down; or production data loss, exposure, or failed payments that has stopped. medium: A failure limited to a few users or one path, a broad internal failure, a production outage that ended on its own, or serious harm outside production. low: No user or system impact, a transient blip, an internal failure on one item or a rare path, or other work outside production, including eval, training, and canary runs.
`--types`	string	No	Comma-separated groups the issue has after the change: reliability, correctness, security, efficiency. A removed group takes its categories with it.
`--categories`	string	No	Comma-separated catalog categories the issue has after the change; each adds its group. One of: outage, silent_failure, regression, performance_degradation, capacity_risk, background_job_failure, dependency_failure, frontend_breakage, data_integrity, business_flow_breakage, configuration_drift, active_attack, suspicious_access, exposure, abuse_and_fraud, agent_misbehavior, cost_anomaly, observability_gap.
`--note`	string	No	Optional context for the change, up to 500 characters. Shown in the issue’s history.

sazabi issues update <issue-id> --severity high --note "Checkout errors reach 3% of requests"  # Raise an issue's severity
sazabi issues update <issue-id> --types reliability,security --categories active_attack --note "Credential stuffing behind the login errors"  # Add security

API

CLI

SDKs

MCP server

Terraform provider

Notifications and limits