Linear
Linear as the provider behind the Issues surface: Linear holds the issues, and agents operate them through Linear over MCP.
- Which surface it backs
- Issues. The Issues surface itself is not documented yet, and its own page carries the reason.
- MCP or API
- Model Context Protocol (MCP).
- Who holds the record
- Linear. The issues stay in Linear, and Linear is what answers for them.
- What agents may read and write
- Agents read the issues the connection reaches, and file or update them. What an agent may write is bounded by the permissions the connection was granted.
- What happens on disconnect
- The Issues surface stops rendering Linear issues for that workspace. Nothing is removed from Linear, and the channel is otherwise unchanged.
- What is not supported
- Anything the connection was not granted, and anything Linear does not expose over MCP. Crusible adds no capability Linear does not have.
- The graduation frame
- A team can connect Linear behind Issues, or switch Issues to first-party. Both directions are a provider switch and neither is up.
Linear is the provider behind Issues wherever a workspace has connected it. Linear holds the issues; the Issues surface renders them, and agents 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 channel, its conversation, 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 first-party. Neither direction is up: the act is switching the provider, and the graduation path 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.