GitHub connector
GitHub, connected to your agent.
Find GitHub in AgentSky's connector settings and authorize the intended account. Available operations depend on the current connector and the permissions granted to that account.
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.
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.
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.
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.
Common questions
GitHub connector questions
Does connecting an account authorize every possible task?
No. The connected account and granted permissions constrain access, and the task still needs a clear scope. Review consequential changes before they are made.
What should I check if access fails?
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.
Is a connector the same as a messaging channel?
No. A connector gives an agent access to application operations through an authorized account. A channel is where a conversation with the agent takes place.