Connect GitHub
Create a GitHub fine-grained personal access token with the right permissions and paste it into Walli-AI.
Connecting GitHub lets an agent read repositories, issues, pull requests and files, and optionally create issues, branches and pull requests. You create a fine-grained personal access token in GitHub, set the permissions below, and paste it into Walli-AI. For what agents do once connected, see GitHub for agents.
Set up the connection
Credential: GitHub personal access token (or: Classic personal access token). Format: github_pat_... or ghp_....
- In GitHub, click your profile picture, then Settings, then Developer settings. Under Personal access tokens choose Fine-grained tokens, then Generate new token. (source)
- Enter a token name, expiration and resource owner. Under Repository access choose the minimal set of repositories the agent needs. (source)
- Under Permissions, set the permissions listed below at the access level shown. (source)
- Choose Generate token. (source)
- Copy the new token and paste it here. (source)
Required scopes
| Scope | What it enables | What breaks without it | Source |
|---|---|---|---|
Metadata: read |
Read repository details | Agents cannot list or look up repositories. | source |
Issues: read |
Read issues | Agents cannot read issues. | source |
Pull requests: read |
Read pull requests | Agents cannot read pull requests. | source |
Contents: read |
Read files and search code | Agents cannot read files or search code. Check with GitHub docs for the permission code search needs. | source |
Optional capabilities
| Scope | What it enables | What breaks without it | Source |
|---|---|---|---|
Issues: write |
Create issues and comments | Agents cannot create issues or add comments. | source |
Contents: write |
Create branches and commit files | Agents cannot create branches or commit files. | source |
Pull requests: write |
Open pull requests | Agents cannot open pull requests. | source |
If a feature says a permission is missing
Open the Integrations page and look at the GitHub connection. It lists the permissions your token is missing and the features each one turns off, and Re-check runs the check again. Create a new token with the permission or repository you need (see the steps above), connect it, then choose Re-check.
Troubleshooting
- An agent cannot see a repository: GitHub lets you limit a token to specific repositories under Repository access (GitHub: personal access tokens), so check the repository was selected when the token was created.
- The token expires: create a new one in GitHub and reconnect.
See also Connecting integrations and channels.