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.
Delegation with predictable routing
Admins set the routing once; after that, every delegated issue lands where it should.
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.
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.
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.
Base branches · auto start · auto-create PR
The routing rules at a glance
An admin connects the workspace once under Settings → Apps → Linear; these rules 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
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 integrationFAQ
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?
Installing or reconnecting the workspace is admin-only, under Settings → Apps → Linear. Once connected, team members use the integration with the org settings already in place.
What if tasks are routed to the wrong project?
Review the team mappings in Settings → Apps → Linear. Unmapped teams always fall back to the default project.
Connect Linear and keep work flowing
Issues keep their context, tasks land in the right project, and PRs follow your existing branch flow.
