---
title: "GitHub connector for agents — authorization and setup — AgentSky"
description: "Connect the account your agent should use for repository work. Connect GitHub to AgentSky with managed OAuth."
url: https://agentsky.dev/connectors/github
---

# GitHub

Where the world builds software. Millions of developers and companies build, ship, and maintain their software on GitHub—the largest and most advanced development platform in the world. Connect your account through managed OAuth to use the available operations in an agent task.

[Repo](https://agentsky.dev/auth/start?returnTo=%2Fconnectors%2Fgithub%3Fresume%3D1)

Connect GitHub using the Connectors control before sending. Authorization opens separately and your draft stays here.

Setup

## Connect GitHub with an explicit scope.

You need an AgentSky account and authority to connect the application account. Start with a read-only task before allowing changes.

01

### Find the application

Open connector settings and search for GitHub. If the catalog is unavailable, retry its load; an unavailable list is not proof the app is unsupported.

02

### Review authorization

Review the OAuth app and requested scopes. Organization restrictions can require an owner's approval; authorization for your personal account does not prove access to a private organization repository.

03

### Verify a bounded task

Ask the agent to inspect a specific repository or issue you are authorized to access and summarize the relevant information without making changes. Name the owner/repository and the exact issue or branch.

Verify access and results

## A connected account is the start of the workflow.

Compare the returned information with GitHub. For later write tasks, inspect the actual branch, issue or pull request and its URL before accepting completion.

- Access troubleshooting If a private repository is inaccessible, check the connected GitHub identity, organization approval and any SAML session requirement. Do not repeatedly reconnect without identifying the denied resource.
- Available actions The runtime discovers the connector's current operations and input requirements. Do not assume every feature in the application's website is available as an agent action.
- Authorize changes explicitly For writes, specify the target and the allowed change. An instruction to draft or analyze is not permission to publish, send or delete.

## GitHub connector questions

## Related resources

[Claude Code + GitHubUse GitHub with Claude Code in the shared Composer.](https://agentsky.dev/agents/claude-code/connectors/github) [Codex + GitHubUse GitHub with Codex in the shared Composer.](https://agentsky.dev/agents/codex/connectors/github) [OpenClaw + GitHubUse GitHub with OpenClaw in the shared Composer.](https://agentsky.dev/agents/openclaw/connectors/github) [OpenCode + GitHubUse GitHub with OpenCode in the shared Composer.](https://agentsky.dev/agents/opencode/connectors/github) [Hermes + GitHubUse GitHub with Hermes in the shared Composer.](https://agentsky.dev/agents/hermes/connectors/github) [Kimi Code + GitHubUse GitHub with Kimi Code in the shared Composer.](https://agentsky.dev/agents/kimi-code/connectors/github) [DeepSeek Harness + GitHubUse GitHub with DeepSeek Harness in the shared Composer.](https://agentsky.dev/agents/dsh/connectors/github) [pi + GitHubUse GitHub with pi in the shared Composer.](https://agentsky.dev/agents/pi/connectors/github) [All connectorsUnderstand managed application access.](https://agentsky.dev/connectors) [ChannelsChoose where the agent conversation happens.](https://agentsky.dev/channels) [PricingReview charges before running work.](https://agentsky.dev/pricing)

## Connect the right GitHub account.

[Open connector settings](https://agentsky.dev/connectors)

## Frequently asked questions

### How does AgentSky connect to GitHub?

The current connector uses OAuth. Authorize the intended GitHub account and review the requested scopes; this flow is not a GitHub App installation.

### Can it work with private repositories?

Access depends on the authorized identity, OAuth scopes and repository permissions. Organization policy or SSO may require an additional authorization step.

### Why can I sign in but still not access an organization repository?

Personal-account authentication does not prove organization access. Check the selected identity, repository permissions and the organization’s OAuth or SSO restrictions.

### Does connecting GitHub allow every possible code change?

No. The connector’s exposed actions and granted scopes define available operations. Your task should also identify the repository, branch and intended change.

### What is a useful first task after connecting?

Ask the agent to read a specific repository file or issue and report its contents with a link. Confirm the correct repository before asking it to make changes.

### How do I remove the connection’s access?

Revoke the OAuth application in GitHub’s account settings when you want to withdraw provider access. Future tasks that require it will need valid authorization again.

### Does connecting the app make agent tasks free?

No. Connection permissions and usage billing are separate. The agent’s model, tools and runtime remain subject to the applicable AgentSky charges.

### Do I need to clone a repository before asking the agent to read an issue?

Issue access and a local repository checkout are different requirements. A connector operation can read an accessible issue without a clone; running code or tests needs the selected agent’s execution environment and appropriate repository access.

### Can I connect my personal account to work on company code?

Only if that account has the required repository access and the organization permits the OAuth application. Personal sign-in by itself does not satisfy organization approval or SSO restrictions.

### What should a repository task specify?

Include owner/repository, branch or revision, and the relevant issue or file. For example, ask for the code paths involved in issue 123 on a named branch instead of a general review of “the repo”.

---

Markdown copy of https://agentsky.dev/connectors/github. Every agentsky.dev page has one: add `.md` to its address or send `Accept: text/markdown`. Start from https://agentsky.dev/llms.txt.
