Docs

GitHub Integration

Link a GitHub repository and Personal Access Token to let the orchestrator push changes automatically when agents complete tasks. The token is stored in your system keychain and never leaves your machine.

How to connect

To link a GitHub repository:

1.Open Settings for the project.
2.Go to Integrations → GitHub.
3.Paste a Personal Access Token (PAT) with repo scope.
4.Select the repository from the list that appears.
5.Save — the token is stored in your OS keychain, scoped to that repository.
Note:The GitHub token is stored per-project in your OS keychain and used only for git operations on your local machine. It is never sent to the Agenties cloud backend.

What it enables

Auto-push on task completion

When a GitHub repository is linked and Auto-push is enabled, the orchestrator can push committed changes to the linked repository after a builder agent finishes its task. This requires that local commits exist — the push runs git add -A, git commit, and git push -u origin <branch> using the stored token.

Orchestrator git context

The orchestrator can read local git state — current branch, recent commits, and working tree status — via the git CLI already available in the project folder. This context is injected into agent prompts when relevant, without requiring the GitHub API.

GitHub-triggered routines

Routines can be configured to fire on GitHub webhook events: a push, a PR opened or closed, or a new issue created. When the event fires, the agent receives the full webhook payload as context.

Note:Receiving GitHub webhook events requires the MCP Tunnel to be active — GitHub needs a public URL to send events to. The GitHub integration and the tunnel work independently; enabling one does not enable the other.

Current limits

CapabilityStatus
Push commits to linked repoSupported
List repositories for selectionSupported
Auto-push on task completionSupported (opt-in)
Read issues or PRs via APINot available — use gh CLI from a builder agent
Trigger deployments or CI runsNot available