See the complete route index at https://crusible.dev/llms.txt before following links.

# Linear

Linear as the provider behind the Issues surface: Linear holds the issues, and agents operate them through Linear over MCP.

<!-- https://crusible.dev/docs/reference/providers/linear/ · doctype: reference · role: both · reviewed: 2026-09-05 -->


Linear is the <a class="docs-term" href="/docs/reference/glossary/#provider">provider</a> behind Issues
wherever a workspace has connected it. Linear holds the issues; the Issues
<a class="docs-term" href="/docs/reference/glossary/#surface">surface</a> renders them, and
<a class="docs-term" href="/docs/reference/glossary/#agent">agents</a> operate them through Linear.

## Who answers for the issues

Linear. An issue's state, its comments, its assignees and its audit trail live
in Linear and are governed by Linear's own controls. A team with five years of
issues in Linear still has five years of issues in Linear after connecting,
and Crusible keeps no second copy to diverge from them.

## What changes in the product

One surface changes. The <a class="docs-term" href="/docs/reference/glossary/#channel">channel</a>, its
<a class="docs-term" href="/docs/reference/glossary/#conversation">conversation</a>, its agent roster
and its permission model are identical either way.

**Planned.** The Issues surface has no screens yet, so this page describes
the connection rather than the surface it renders into. The Issues reference
page carries the same notice.


## What an agent can reach

An agent acts as the connection. It reads the issues the connection was given
and files or updates only what the connection permits.

The permissions a connection holds are set once and apply to every agent that
uses it. Narrowing them narrows what every agent in every channel can reach
through Linear, which is why the connection rather than the individual agent
is where a question about access is answered.

## Switching in either direction

A team can connect Linear behind Issues, or switch Issues to
<a class="docs-term" href="/docs/reference/glossary/#first-party">first-party</a>. Neither direction is
up: the act is switching the provider, and the
<a class="docs-term" href="/docs/reference/glossary/#graduation-path">graduation path</a> runs both ways.
Whichever way a workspace goes, the issues it had before the switch are still
held by whichever tool held them, and no issue is copied anywhere by the act
of switching.