GitHub

What your agent can do

On an agent with a sandbox, pick Full toolkit (recommended) for GitHub in the agent’s Integrations section. The agent then uses the GitHub CLI and git, signed in with your connection, so it can:

• Clone repositories and read their contents
• Create, list, comment on and close issues
• Open, review, check out and merge pull requests
• Create branches, commit and push
• Read GitHub Actions run status
• Create and list releases

With Lightweight, or without a sandbox, the agent can list repositories, list issues and create issues.

---

Connecting GitHub

1. Go to Console → Integrations → GitHub
2. Click Connect GitHub, then Connect with OAuth. (The API Key / Token tab takes a personal access token instead.)
3. You’ll be redirected to GitHub’s authorization page
4. Review the access and approve it

Personal vs. bot account

A personal GitHub connection acts as you. On a team, it is shared with your team unless you choose otherwise when you connect; on your own, it is private to you. It’s automatically revoked when you’re offboarded. A GitHub bot account (a GitHub user created specifically for this purpose) is shared with the team and stays durable if any one member leaves. For team use, connect with a bot account rather than a personal one.

---

Permissions

The connection asks GitHub for the repo, read:org and read:user scopes.

You narrow that per agent, in the agent’s Integrations section:

• Abilities start read-only. Turn on Allow writes only when the agent needs to change things.
• All Repositories or Select Repositories sets which repositories this agent may work in.

---

Example tasks

• “Check the open issues in acme/backend labeled ‘bug’ and summarize them”
• “Create a GitHub issue: title ‘Login timeout’, priority High, assigned to @alice”
• “Review the diff in PR #42 and flag any obvious security issues”
• “List all PRs waiting for review that are older than 3 days”
• “What was the last commit message on the main branch?”