DOCUMENTATION / Connect tools
GitHub
Install your own GitHub App so agents can verify product behavior against repository source.
GitHub uses your own GitHub App with Contents: read-only permission. Install it on the repositories you choose. Jak reads source code and returns commit-pinned citations; it does not write code or open pull requests through this connector.
Register the app
- In your GitHub account or organization settings, open Developer settings → GitHub Apps → New GitHub App.
- Give it a recognizable unique name and a homepage URL.
- In Jak, select the product and open Tools → Providers → GitHub → Connect GitHub App. Copy the displayed user authorization callback URL.
- Put that URL in the GitHub App’s Callback URL setting. Its path ends in
/api/v1/oauth/github/callback. - Under repository permissions, set Contents to Read-only. Leave unrelated permissions unrequested. This read connector does not need webhook delivery; disable Active under Webhook if you are creating the app solely for Jak.
- Create the app, generate a Client secret, and copy the Client ID.
- Under Install App, install it on the account and repositories you want Jak to read.
Use GitHub’s app registration guide for account or organization-specific details. The Client ID differs from the numeric App ID, and this connection does not ask for a private key or personal access token.
Authorize in Jak
Enter GitHub App client ID and GitHub App client secret, then choose Continue to GitHub. Authorize with a GitHub user who can access the selected repositories.
Both app installation and user access matter. Authorizing the app without installing it on a repository does not make that repository available.
Try it
Ask Cody:
Find the repository for this product and inspect the onboarding implementation. Explain the steps a new user takes and cite the source files at the commit you inspected. Flag anything you cannot verify from code.
The connection supports repository discovery, finding source file paths, and reading numbered source lines with bounded results. File discovery matches paths rather than searching file contents.
If something goes wrong
Check installation scope, Contents permission, and the authorizing user’s repository access. If authorization fails, verify the callback rather than the app’s setup URL. localhost and 127.0.0.1 differ; register the addresses you actually use. See GitHub’s callback guide.