GitHub Setup Guide
Connect GitHub to Oskuo using a fine-grained personal access token so Oskuo can help you manage issues, pull requests, and repositories.
Prerequisites
- check_circle A GitHub account (personal or organisation member)
- check_circle Access to the repositories you want Oskuo to manage
- check_circle An active Oskuo account on any plan
Connecting GitHub to Oskuo
- 1 Go to github.com/settings/tokens?type=beta and click Generate new token to create a fine-grained personal access token.
- 2 Give the token a name (e.g. "Oskuo") and set an expiry. Under Repository access, select the repositories you want Oskuo to access.
- 3 Under Repository permissions, set Issues to Read and write. Optionally enable Pull requests: Read to list PRs. Metadata: Read is added automatically.
-
4
Click Generate token and copy it — it starts with
github_pat_and will only be shown once. - 5 Open Settings → Connectors in Oskuo, find GitHub, paste the token, and enter your default owner (your username or organisation name). Click Test & Save.
What you can do
- check_circle List repositories accessible to the token
- check_circle List, get, and create issues
- check_circle Add comments to issues
- check_circle Close issues
- check_circle Set and manage labels on issues
- check_circle List available labels for a repository
- check_circle List pull requests
Try it out
Here are some things you can ask Oskuo to do:
- chat_bubble "Show open issues labelled 'bug' in my-app"
- chat_bubble "Create an issue about login page performance"
- chat_bubble "List my open PRs"
- chat_bubble "Close issue #42 and leave a comment saying it's been fixed in v2.1"
Good to know
- info Oskuo can't merge pull requests or push code — it works with issues, comments, and labels.
- info GitHub Actions workflows can't be triggered or managed through Oskuo.
- info Oskuo can only access repositories included in your token's scope — private repos need to be explicitly granted.
- info The Default Owner field is used when you don't specify a repository owner in your prompt. Set it to your username or organisation name.
Keeping things secure
- lock Your personal access token is encrypted with AES-256-GCM before it's stored — Oskuo never keeps it in plain text.
- lock Always use fine-grained tokens (not classic tokens). They let you limit access to specific repositories and permissions.
- lock Set an expiry date on your token and rotate it regularly. GitHub lets you create tokens that expire automatically after 30, 60, or 90 days.
- lock All requests to the GitHub API are made over HTTPS, so your repository data is encrypted in transit.
Troubleshooting
Authentication fails with a 401 error expand_more
The token may have expired or been revoked. Generate a new fine-grained token at github.com/settings/tokens and update Oskuo with the new value.
Repository returns a 404 error expand_more
The fine-grained token doesn't have access to that repository. Edit the token on GitHub to add the repository, or generate a new token that includes it.
"Default owner not set" error expand_more
The Default Owner field in the connector settings is empty. Open Settings → Connectors → GitHub and enter your GitHub username or organisation name, then save.