ClawNode
Connect your agent to GitHub
GitHub access lets your agent inspect repositories, summarize pull requests, and help with issue triage. Use a scoped token with least privilege so automation stays useful and safe.
Tip: Prefer a dedicated bot account for org repos. It makes access reviews and token rotation easier.
1
Choose the GitHub account to authorize
- Use a dedicated bot/service account when possible.
- Grant that account access only to the repositories your agent needs.
- Confirm org SSO requirements before creating the token.
2
Create a fine-grained personal access token
- Go to GitHub → Settings → Developer settings → Personal access tokens.
- Create a Fine-grained token with an expiration date.
- Select only required repositories and minimum permissions (for example: Issues and Pull requests).
- Copy the token once and store it securely.
If your organization requires SSO authorization, approve the token for the organization before testing.
3
Add the token to your agent
- Add the value in your integration secrets as
GITHUB_TOKEN(or your integration key name). - Reload your agent/integration settings.
- Ask your agent to verify it can list repositories and read issues.
4
Verify with practical prompts
- "List open pull requests in repo X and summarize risk."
- "Find stale issues with no updates in 14 days."
- "Draft a release note from merged PRs in the last week."
Also useful: connect your agent to Linear so planning and code work stay connected.