GitHub
Issues, pull requests and code search across the repositories your token can read.
What you will be asked for
- Personal access tokenSecret
Where to find these
GitHub runs this service itself, so there is nothing for you to run. You only need a token, and Worclaude sees exactly what that token can see.
Personal access token
Prefer a fine-grained token: it is scoped to the repositories you pick, which a classic token is not.
- github.com/settings/personal-access-tokens → Generate new token (or: your avatar → Settings → Developer settings → Personal access tokens → Fine-grained tokens).
- Name it
Worclaudeand set an expiry. 90 days is a sensible default. - Resource owner: yourself, or the organisation whose repositories you need. An organisation may require an admin to approve the token before it works; if answers come back empty, that approval is usually why.
- Repository access: pick only the repositories you actually want readable. "All repositories" is rarely what you mean.
- Permissions → Repository permissions, all Read-only:
- Contents: the code and its history
- Issues: issues and their comments
- Pull requests: PRs, reviews and diffs
- Metadata: required, and GitHub ticks it for you
- Generate token and copy it. GitHub shows it once.
A classic token works too, with the
reposcope, butrepoalso grants write to every repository you can reach, and nothing here needs that.
Connect this source
About a minute, once you have the credentials.