From task to merged PR
Install the GitHub App, pick your repos, and hand tasks to agents. They clone, branch, and open PRs from capy/ branches — main only moves through your own review and merge.
Built around your review process
Agents follow the same rules as any engineer on the repo: isolated branches, reviewed pull requests, scoped access.
Isolated branches, reviewed PRs
Agents work on capy/<task-slug>-<id> and never push to your default branch. When the diff holds up, click Create PR — it lands on GitHub, where your CI, checks, and reviewers take over.
capy/<task-slug>-<id> → Create PR → your merge flow
You choose the repositories
Grant the App specific repos at install and change the list anytime in your GitHub settings — no personal tokens to issue or rotate.
Repo access lives in your GitHub settings
Issues brief the agent
Link a GitHub issue to a task and the agent reads it before writing code, so the change matches what was actually reported.
Linked issue → task context
Install once, four scopes
Click Connect GitHub in the dashboard, pick your repositories, and the App is in — requesting only the scopes the workflow uses. No tokens, no YAML.
Requested scopes
- Contents — read and write code in selected repos
- Pull requests — open PRs from finished tasks
- Issues — read issues for task context
- Metadata — repo info like branch names
Other integrations
The rest of the stack Capy connects to.
Linear
Delegate issues; team mappings and branch defaults route them to the right code.
View integrationFAQ
Branch rules, repo access, and troubleshooting.
Does Capy push directly to my main branch?
Never. Every task runs on its own capy/<task-slug>-<id> branch. You review the diff and create a PR; main only changes through your normal merge process.
Can I limit which repos Capy can access?
Yes. You pick specific repositories when installing the GitHub App, and you can update the list anytime in GitHub settings without reinstalling.
What if my repo doesn't appear in Capy?
Check that the App is installed and the repo is selected in your GitHub settings. After org permission changes, you may need to re-authorize.
What if a push fails?
Make sure you're on a capy/* working branch — Capy never pushes to your default branch. If org permissions changed recently, re-authorize the App.
Connect GitHub and start shipping
One install. Agents take the branches and PRs; you keep the review.
