GitHub integration

From task to merged PR

Connect your GitHub repos and let agents do the coding. They clone, branch, commit, and open PRs. Your main branch stays clean, your review process stays the same.

Get started Read the docs

How Capy works with GitHub

Built for how engineering teams actually work with GitHub.

Automatic branching

Every task gets its own branch (capy/<task-slug>-<id>). Your main branch stays clean, and agents never push directly to it.

One-click PRs

Review the diff in Capy, then click Create PR in the diff view. The pull request lands on GitHub ready for your normal review and merge workflow.

Repo-level access control

Choose exactly which repositories agents can access. You can update repo access anytime in your GitHub settings, with no tokens to rotate.

Issue context

Agents read GitHub issues for context when working on tasks. Link an issue to a task and the agent uses it to understand what needs to be built.

Setup in 3 steps

One-click install. No tokens. No YAML.

Step 1

Install

Install the Capy GitHub App from the dashboard by clicking Connect GitHub. Choose which repositories to grant access to.

Step 2

Task

Start a task and pick your repo. It's cloned automatically, the agent creates a branch (capy/<task-slug>-<id>), and gets to work.

Step 3

Merge

Review the diff, click Create PR in the diff view, and merge on GitHub. Your existing CI, checks, and review process all apply.

FAQ

Common questions about the GitHub integration.

Does Capy push directly to my main branch?+

Never. Every task runs on its own branch (capy/<task-slug>-<id>). You review the diff and create a PR, and your main branch is only updated through your normal merge process.

Can I limit which repos Capy can access?+

Yes. When installing the GitHub App, you choose specific repositories. You can update this anytime in your GitHub settings without reinstalling.

What if my repo doesn't appear in Capy?+

Check that the GitHub App is installed and you've selected the repo in your GitHub settings. If you recently changed org permissions, you may need to re-authorize.

What if a push fails?+

Make sure you're on a working branch (capy/*). Capy never pushes directly to your default branch. If you recently changed org permissions, you may need to re-authorize the GitHub App.