Skip to main content
Connect GitHub to let selected agents browse code, search repositories, and work with issues and pull requests. The token and agent tool choices control what they can access.

​
What you unlock

Repository access

Browse repositories, view files, and search code within the access granted to the connected token.

Issue management

Create, update, and search issues. Assign labels, milestones, and team members directly from chat.

Pull request workflows

Review pull requests, check CI status, and manage branches through your agent.

Actions & workflows

Monitor GitHub Actions, view workflow runs, and track deployment status.

​
Connect GitHub

1

Open Settings → Integrations

In any workspace go to Settings → Integrations and select GitHub.
2

Create a Personal Access Token

Go to github.com/settings/tokens, create a Personal Access Token (classic) with repo, read:org, and read:user scopes, and copy it.
3

Paste and connect

Paste the token into the API Key field and click Connect.
Use a fine-grained token or a classic token scoped to only the repositories and permissions your agent needs. Avoid using tokens with full admin access unless necessary.

​
Agent tools

Add GitHub tools to agents that need them. Their access is limited by the connected token and selected tools.

​
Repositories & Code

​
Issues & Pull Requests

​
Actions & Workflows

​
Triggers

Automated triggers for GitHub are not yet available. Triggers will be added in a future update — check back soon.

​
Example use cases

Ask your agent “Find where we handle authentication in the backend” and it searches across your repositories, returning relevant file paths and code snippets.
An agent lists open pull requests across your team’s repositories each morning and posts a summary to your #engineering channel — highlighting PRs waiting for review, CI failures, and stale PRs.
When someone reports a bug in chat, ask your agent to create a GitHub issue with the right labels, assignee, and milestone — all populated from the conversation.

​
Troubleshooting

Make sure the token was created at github.com/settings/tokens and has the required scopes: repo, read:org, and read:user. If using a fine-grained token, verify it has access to the specific repositories you need.
Classic tokens need the repo scope for private repository access. Fine-grained tokens need explicit repository access grants. Check your token configuration in GitHub.
GitHub has API rate limits (5,000 requests/hour for authenticated users). If you hit limits, wait for the reset window or reduce the frequency of agent queries.
If your token has read:org scope but you still can’t see org repos, check that the token is authorized for your organization under GitHub’s Settings → Applications → Authorized OAuth Apps or SSO settings.

Back to Integrations

View all available integrations