> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zelto.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Linear

> File a Linear issue from a Zelto finding or solution and keep its status in sync as the issue moves.

## Connect

1. Open **Settings → Integrations → Linear** and click **Connect Linear**.
2. Authorize Zelto on the Linear workspace you want to file issues into.

Once connected, the card shows the workspace name and the install date.
Connecting grants Zelto read and write access so it can create issues and read
their state back.

## Choose the allowed team

Zelto is scoped to **one** Linear team. After connecting, pick the team under
**Settings → Integrations → Linear → Allowed team**. Everything Zelto does in
Linear — filing issues from findings and solutions and the chat actions below —
stays inside this team; issues in other teams are never read or changed.

<Note>
  Until a team is selected the integration is inactive: filing an issue from a
  finding, a solution, or from chat returns "Select a Linear team in Settings →
  Integrations first." Change the team anytime — it takes effect immediately.
</Note>

## Open an issue from a finding

From any [finding](/docs/findings) detail page, click **Create Linear issue**. Zelto:

* Pre-fills the issue title and description from the finding.
* Adds a link back to the Zelto finding in the description.
* Files it in your selected team.

A finding holds **one** Linear issue at a time — Zelto won't open a second. Once
linked, the finding shows a chip with the issue identifier and its current
state; click it to open the issue in Linear.

## State sync

After an issue is linked, Zelto keeps the finding in step with it, so you don't
have to update both by hand:

* The issue's state shows on the finding chip and stays current as the issue
  moves through your Linear workflow.
* Marking the issue **Done** sets the finding to **Resolved**.
* **Canceling** the issue sets the finding to **Ignored**.
* Any other state (Todo, In Progress, Backlog…) updates the chip but leaves the
  finding's status alone.
* **Deleting** the issue in Linear clears the link, freeing the finding so you
  can file a new one.

<Note>
  Sync runs one way after creation: Linear → Zelto. Closing or canceling a
  linked issue moves the finding's status, but changing a finding's status in
  Zelto does not move the Linear issue.
</Note>

## Open an issue from a solution

You can also file a Linear issue straight from a [solution](/docs/solutions).
From any solution detail page, click **Create Linear issue**. Zelto:

* Pre-fills the issue title (or "Solution for {agent}" when the solution has no
  title yet) and description from the solution.
* Adds a link back to the Zelto solution in the description.
* Files it in your selected team.

Like findings, a solution holds **one** Linear issue at a time, and the linked
issue shows as a chip with its identifier and current state.

State sync mirrors the solution side the same way:

* Marking the issue **Done** sets the solution to **Done** (and publishes it if
  it was still a draft).
* **Canceling** the issue sets the solution to **Cancelled**.
* Any other state updates the chip but leaves the solution's status alone.
* **Deleting** the issue in Linear clears the link.

## From chat

When Linear is connected and a team is selected, you can drive Linear from the
Zelto chat without leaving the app. The assistant can:

* **List issues** in the selected team, optionally filtered by a title search.
* **Look up an issue** by identifier (e.g. `ENG-42`) or id, with its description
  and current state.
* **Create an issue** in the selected team.
* **Update an issue** — title, description, priority, or workflow state.

Creating or updating an issue is a write, so the chat shows a confirmation card
first; nothing changes until you approve it. Every action is hard-scoped to the
selected team — asking the assistant to touch an issue in another team returns
an error rather than crossing the boundary.

## Disconnecting

**Disconnect** stops Zelto using the connection and removes the stored workspace.
Existing issues stay in Linear; new issues can't be opened until you reconnect.

## Related

* [Findings](/docs/findings) — the issues you push into Linear.
* [Solutions](/docs/solutions) — fixes you can file into Linear the same way.
* [Triage findings](/docs/guides/triage-findings) — where filing to Linear fits in the workflow.
* [Integrations](/docs/integrations) — every connector in one place.