Capabilities
Once connected, your agent can interact with GitHub repositories via the API.- List repositories
- Read file contents
- Create and update files
- Create pull requests
- Create and manage issues
- List branches and commits
- Trigger GitHub Actions workflows
- Monitor workflow runs and read logs
- Cancel or re-run workflows
- Download workflow artifacts
Setup Guide
Follow these steps to connect GitHub to your instances.1. Create a Personal Access Token on GitHub
Go to GitHub Settings → Developer Settings → Fine-grained tokens- Select specific repositories you want to grant access
- We recommend enabling read and write access to Contents and Pull requests for the repos you care about
- To use GitHub Actions, also enable read and write access to Actions
- Choose an expiration date (90 days recommended)
- Copy the generated token immediately because you won’t see it again
2. Store the token in Environment
Go to Environment and create a new variable.-
Name: Use a descriptive name like:
GITHUB_TOKENfor all reposGITHUB_TOKEN_PERSONALfor personal reposGITHUB_TOKEN_WORKfor work repos
- Value: Paste the GitHub token you copied
3. Grant access to instances
Choose how instances should access this token:- Option A: Global Secret (All instances) — Toggle “Make globally accessible” when creating the secret. All instances automatically have access.
- Option B: Instance-Specific (Selective access) — In Environment, open the secret and grant the specific instance access. This lets you control exactly which instances can use which tokens.
Multiple Tokens
You can create multiple GitHub tokens for different purposes. This lets you grant different instances access to different repositories by controlling which token they use.GITHUB_TOKEN_PERSONAL→ Personal repositoriesGITHUB_TOKEN_WORK→ Work repositoriesGITHUB_TOKEN_OPENSOURCE→ Open source projectsGITHUB_TOKEN_MYCOMPANY→ Organization-specific repos