Sazabi and Linear: turn investigations into tickets, and ask from the ticket

Last verified on Nov 8, 2026.

A finding that never becomes a ticket tends to be forgotten. A ticket that has no evidence attached tends to be ignored. Sazabi is AI-native observability and security, and its Linear integration is meant to close that gap from both sides: the agent files and maintains the issue, and you can start the agent from the issue.

What Sazabi does with Linear

Linear is an issue tracker integration with two connection methods, each configured on its own.

Core integration. You authorize through Linear OAuth, and the connection acts for the authorizing workspace, so tickets Sazabi files show up attributed to the connected app. During an investigation the agent can create a Linear issue and keep it current: update fields, move it through your workflow states, add comments, and link it back to the Sazabi issue or thread. Linear is also an agent surface. Assign the Sazabi agent to an issue, or mention it in a comment, with a free-form request. It investigates against your project's data and posts the answer back in Linear, and follow-up prompts in that thread continue the work.

MCP connector. This one gives the agent Linear's tools, with read and write access. It can search and filter issues across teams and projects, create, update and triage issues, browse projects, cycles and roadmap items, and manage labels, priorities and assignees. Authorization uses OAuth with dynamic client registration, and Sazabi refreshes the token afterwards.

Linked issues carry one more behavior. If a Sazabi issue is linked to a Linear task that syncs status, that task decides when the issue closes.

Questions it answers

• Is there already a Linear issue for this error, and who has it?
• What is the status of the ticket tied to this Sazabi issue?
• Which open issues on the platform team are about the same service?
• What does the agent find when asked to look into this ticket?
• Which cycle will pick up the fix?

A worked example: delegating a ticket to the agent

Your team has a Linear issue, PAY-482, saying checkout confirmations fail intermittently. Instead of copying logs into it, an engineer assigns the Sazabi agent. Names and IDs below are invented.

PAY-482  Intermittent failures on checkout confirmation
Assignee: Dana Wu        Delegate: Sazabi

Dana Wu   @Sazabi what changed around the first failure, and which service is affected?
Sazabi    (comment) Findings from the project's data, with a link back to the Sazabi thread
Dana Wu   @Sazabi does the same error appear in the orders service?

Linear's agent documentation explains the wording in that header. Assigning an issue to an app sets it as the issue's delegate, not its assignee, so a human keeps ownership while the agent works on their behalf. Linear agents are installed by a workspace admin through OAuth with actor=app, and the app:assignable and app:mentionable scopes control whether they can be delegated issues and mentioned. A mention or delegation is what starts a conversation, which fits Sazabi's description: you ask from Linear, and the answer lands in Linear.

The Sazabi docs add that the agent can then keep the ticket current as the investigation moves, and that you can link your own Linear account under connected accounts so it files as you. When a personal connection exists, Sazabi uses it first and otherwise falls back to the organization integration.

How it fits with other integrations

Linear competes for the same slot as Jira: one tracker per team is typical. Pair it with GitHub so the agent can search your code while it works a ticket, and with Slack to see new issues where the team talks. Linear's MCP server is hosted at mcp.linear.app/mcp. See the integrations index for all methods, or pricing.