NewCapy V2 is here
Linear integration

From Linear issue to merged code

Delegate issues without leaving Linear. Team mappings route each one to the right Capy project, branch defaults point at the right code, and the issue itself rides along as context.

Get startedRead the docs
Mission control console
Capy in a captain's hat

Delegation with predictable routing

Admins set the routing once; after that, every delegated issue lands where it should and its progress streams back into the issue.

Hand off without switching tools

Start work from the issue itself. Capy picks it up with the issue as context and gets going — no copying descriptions into a prompt.

Capy carried through the clouds by a pelican

Issue → running task

Teams map to projects

Map each Linear team to a Capy project so delegated work lands on the right codebase. Teams without a mapping fall back to your default project.

Capy and pelican team photo

Unmapped teams → default project

Predictable from branch to PR

Set the base branch Linear-origin runs start from, per repository, and use org-level controls to decide whether delegated tasks start automatically and open a PR when they finish.

Hand-drawn gear

Base branches · auto start · auto-create PR

The routing rules at a glance

Any member connects the workspace once under Settings → Integrations → Linear; admins set the routing rules that handle everything after.

Org configuration

  • One Linear workspace per organization
  • Default project for unmapped teams
  • Team → project mappings
  • Per-repo base branches
  • Auto start on delegation
  • Auto-create PR on finish
  • Issue context inside Capy
Database illustration

Other integrations

The rest of the stack Capy connects to.

GitHub

Agents branch, commit, and open PRs. Main only moves through your merge process.

View integration

Slack

Tag @Capy in a thread and it becomes a task, with the conversation as context.

View integration

Vercel

Preview URLs from Vercel appear beside the diff in every PR review.

View integration

FAQ

Routing, branches, and admin setup.

How does Capy choose the project for a Linear issue?+
It checks for a team mapping first. If none exists, the issue goes to your configured default project for Linear.
Can I control which branch Linear tasks use?+
Yes. Set default branches per repository under your Linear app settings — Linear-origin runs use them as base branches.
Do I need to be an admin to connect Linear?+
No. Any org member can install, reconnect, or disconnect the workspace from Settings → Integrations → Linear. Changing team mappings, the default project, or branch defaults requires an org admin or owner.
Does mentioning @Capy in an issue start work?+
No. Capy only acts on issues delegated or assigned to the Capy agent; that creates a Linear agent session mapped to one Capy thread. Comments on an issue without a session do nothing, and comments inside the session continue the same thread.
What if tasks are routed to the wrong project?+
Review the team mappings in Settings → Integrations → Linear. Unmapped teams fall back to the default project, and an already-running session keeps its original project even after you fix the mapping.

Connect Linear and keep work flowing

Issues keep their context, tasks land in the right project, and PRs follow your existing branch flow.

Get startedContact Sales
Capys leaping through comic panels