Linear
Connect Linear so your team can hand issues to Capy without leaving Linear. Delegating an issue starts a Capy thread, and everything the agent does streams back into the issue as native agent session activity: progress, responses, the plan, and a link to the thread.
Connect Linear
Any org member can install the connection from Linear settings. One Linear workspace connects to one Capy org. Admins and owners can map Linear teams to Capy projects and set a default project.
Each person links their Linear account to their Capy account once. Capy prompts unlinked users in Linear the first time they delegate. Capy never matches accounts automatically by email or name.
How delegation works
Assigning or delegating an issue to the Capy agent creates a native Linear agent session, and that session maps one-to-one to a Capy thread. Later prompts and comments inside the agent session continue the same thread.
The session is the boundary: a comment on an ordinary issue with no Capy agent session does nothing. If you want Capy on an issue, delegate it; mentioning or commenting won't start anything.
When a session starts, Capy may move the issue into the team's first started state and set itself as the assignee when nobody else is assigned. The first prompt carries the issue identifier, title, description, URL, and requester, so the thread starts with real context; later prompts carry only the new comment.
Project routing
A new session picks its Capy project deterministically:
- The Linear team's mapping, when one exists.
- Otherwise the connection's default project.
- Otherwise a persistent error in Linear pointing at Capy's connection settings; Capy never guesses a project.
Routing fails closed: a stale mapping, or a mapping the delegating user can't access, produces a visible configuration error instead of silently landing in a different project. An existing session keeps its project even if mappings change later.
Default branches
Set per-repository default branches for Linear-origin threads in the connection settings. A repository without an entry falls back to its project default. These apply only to repositories already attached to the selected project.
What Capy posts back
Capy projects thread activity into the agent session as native Linear activity:
- Short thought and action updates while the agent works.
- Persistent responses for each message the agent sends you.
- A thought when the agent hits an error, and one persistent response if the run ends on it.
- A selection prompt when the agent needs a clarifying answer.
- The Capy thread URL as the session's external link, so you can jump into the full transcript any time.
Markdown and file attachments are lowered to what Linear supports, with files as attachment links.
Stopping a session
Linear's stop signal interrupts the thread's current run. It doesn't archive the thread or break the session mapping; a later prompt in the same session starts a fresh run.
Permissions and scope
- The connection is org-level: one Linear workspace per Capy org.
- Any enabled member can install, reconnect, or disconnect the connection; team mappings, the default project, and branch defaults require an admin or owner.
- Every inbound action re-checks the actor's identity link and current org membership: leaving the org revokes access immediately, and links don't grandfather.
- If Linear revokes the app's authorization, the connection flips to a reconnect state that preserves your mappings; reconnecting restores everything.