Connect GitHub
Let your AI employee read and push code to your GitHub repositories from inside development workrooms.
GitHub token settingsWhy we ask for this
Development workrooms need to clone your repository to work on it and push commits back when changes are ready. GitHub requires an authenticated credential for both.
A fine-grained token (or OAuth connection) lets you grant exactly the repositories and actions you want — nothing more — and revoke it instantly if you ever need to.
The token is encrypted at rest and only decrypted and injected as GITHUB_TOKEN when a dev session starts. It never appears in logs or in the app you publish.
Where to get a token
- 1The easiest path is to click "Connect" on the GitHub card and authorise via OAuth — no manual token needed.
- 2To use a token instead, open GitHub → Settings → Developer settings → Personal access tokens.
- 3Prefer a fine-grained token scoped to only the repositories the AI employee should touch.
- 4Grant Contents (read/write) and, if it should open pull requests, Pull requests (read/write).
- 5Copy the token (it starts with "github_pat_" or "ghp_") and paste it into the integration field.
Fine-grained vs classic tokens
Classic tokens grant broad account-wide access; fine-grained tokens are scoped per-repository and per-permission. Always prefer fine-grained for an automated agent so a leaked token cannot reach your whole account.