GitHub
With a repository connected, an agent can read code, push changes, handle issues and pull requests, and report progress back.
Add a repository
Section titled “Add a repository”Open GitHub → Add repository:
| Field | Notes |
|---|---|
| Repository | owner/repo, or just repo to auto-create a private repository |
| Admin token | Requires repo scope; masked after saving |
| Visibility | Public/private, applied when creating a repository |
After saving you can see connection status, default branch and webhook configuration.
Team and permissions
Section titled “Team and permissions”Repository details let you manage members:
- Invite team members
- Bind a system account
- See whether access and tokens are in place
Status badges read “has access / not bound / missing token / invited”; follow the badge.
Webhooks
Section titled “Webhooks”Used to send GitHub events back to the platform (for example, an issue comment triggering an agent). Toggle per event type; unconfigured shows “not configured”.
Use in a session
Section titled “Use in a session”- Ask the agent to clone or read the repository, create a branch, commit changes.
- Prefer Exchange Space for credentials; never paste tokens into the chat.
- For large changes, ask for a plan before committing.
Clone fails / 403 — token expired, missing repository permission, or SSO not authorised.
Push rejected — branch protection or insufficient permission; the token needs write access.
Webhook does not fire — check the event type is enabled and the delivery log on GitHub.
Repository not listed — verify spelling and account permissions; organisation repos may need extra authorisation.