Independent guide · Last updated August 20, 2026
Connect GitHub to Claude Cowork: setup, permissions, and workflows
Use GitHub in Cowork to understand repository work, triage issues, review pull-request context, and turn project activity into useful next steps—while keeping the connection scoped to the access you intend to grant.
GitHub connector: What you should know
The GitHub connector is one of the most useful integrations for development teams. It lets Claude read and, when configured, write to your repositories. Use it to triage issues, summarize pull requests, research codebase architecture, and automate repetitive repository maintenance. Start with read-only workflows to build confidence, then expand to write operations once you've tested the patterns.
Before you connect
- Cowork requires an eligible paid Claude plan. Availability can vary by plan, workspace policy, and country.
- You need a GitHub account with access to the repositories you want Claude to reference.
- For organization repositories, check whether your GitHub organization or Claude workspace administrator restricts third-party app access.
This is an independent guide. Confirm the current availability and permission screen in Claude before authorizing access.
How to connect GitHub to Cowork
- Open Claude and go to Customize → Connectors.
- Find GitHub and select the option to connect.
- Sign in to GitHub when prompted and review the repositories and permissions shown on the authorization screen.
- Return to Cowork and ask a narrow first question about a repository, issue, or pull request to confirm the connection behaves as expected.
If your UI differs, use Claude’s current connector documentation as the source of truth.
Start with read-only, high-value tasks
The most reliable first use cases ask Cowork to synthesize existing work before you rely on it for actions that change a repository.
Issue triage
“Review open issues in owner/repo. Group duplicates, flag stale reports, and give me a short prioritized triage list with issue links.”
Pull-request briefing
“Summarize the open pull requests in owner/repo: the problem each addresses, files changed, unresolved review comments, and the safest next action.”
Release-note draft
“From merged pull requests since the last release, draft customer-facing release notes. Separate confirmed changes from anything that needs an owner to verify.”
Permission and safety checklist
- Review the exact repositories and scopes before completing GitHub authorization.
- Use a personal test repository first when evaluating a new workflow.
- Keep secrets, production credentials, and sensitive incident details out of prompts unless your organization explicitly permits that use.
- Review any proposed write action before approving it; connector capabilities and confirmation behavior can change.
- Revoke the connection from the relevant Claude or GitHub settings if the access is no longer needed.
Troubleshooting
- GitHub does not appear in the connector directory
- Check your Claude plan, workspace policy, and country availability. In managed organizations, an administrator may need to approve the connection. GitHub connector is available on Pro, Max, Team, and Enterprise plans.
- Cowork cannot see a repository
- Confirm that the authorized GitHub account has access to the repository, then revisit the connection’s repository selection in Claude settings. Check whether your GitHub organization’s app policy restricts third-party integrations. If access was just granted, wait a moment and try again.
- The result is too broad or misses the point
- Be explicit about what you want: name the specific repository, specify a time window or branch, request a particular output format (summary, prioritized list, action plan), and clarify whether you need Claude to flag anything requiring human review.
- Cowork proposed a write that I don’t want to approve
- Never approve a proposed action you’re unsure about. Revoke the GitHub connector’s write permissions in Claude settings if you only need read access, or ask Claude to first simulate the change without applying it.
GitHub workflow guides
Once connected, choose the GitHub task that matches your needs. Each guide includes setup, prompts, and best practices:
Automate workflows
Run repeatable repository tasks and automate issue management with GitHub Actions.
Triage issues
Prioritize and organize your issue backlog efficiently with Claude.
Summarize pull requests
Understand changes, review impact, and approve faster with context summaries.
Research repositories
Analyze codebase architecture, tech debt, and dependencies.
Common GitHub workflows
Safety and official sources
Official resources
- → github.com official site
- → docs.github.com for API docs
- → support.claude.com for Cowork help
Before connecting
- Review GitHub permission scopes
- Start with read-only workflows
- Review before approving writes
Build the next step
Pair this connection with a repeatable recipe and a prompt pack rather than relying on a one-off chat.
Last updated: August 20, 2026 · Independent resource: Learn more about this site
Related connectors
More guides for connecting your tools to Claude Cowork.