GitHub

Connect GitHub to let agents work with repositories through git and gh, and let repository events start routines. The workspace installation and each person's account are separate connections.

Connect an installation and your account

In Settings → Workspace integrations, choose GitHub and Install for workspace. Choose the GitHub organisation or account and the repositories the App may access, then finish the account authorization. The person installing the App links their own account during this flow.

Connections and installation pickers show the GitHub organisation or account login when available. Existing installations pick up this name without reinstalling; the installation ID is used as a fallback if GitHub cannot return it.

Other members choose Link my account on that installation. This gives Standards their own GitHub identity. Installing the App does not share the installer's personal token with the workspace. If the GitHub card is absent, the deployment has not enabled this integration; dedicated-instance setup is described in Dedicated instances.

Give an agent GitHub access

In an agent or routine's Tools, add the GitHub installation. The agent needs a sandbox, or an environment with a harness that provides a terminal. Adding GitHub access also enables the Sandbox tool group when needed; if you cannot grant Sandbox to that routine, the picker explains the required permission. It uses git and gh; there is no separate set of GitHub tools to learn.

Runs use the linked account of their authority: the person whose permissions the conversation or routine acts under. A routine acts for its trigger or schedule author. A missing personal connection does not fall back to the installer. Link that person's account before running work that needs GitHub.

The installation grant enables a personal credential. It does not restrict that credential to the selected installation. Its reach is the person's GitHub access intersected with the App's permissions, across all installations available to that account. GitHub access has no separate read and write toggle in Standards; GitHub's own permissions still apply. An explicit GH_TOKEN or GITHUB_TOKEN Variable takes precedence over the managed credential.

Repositories and events

An environment can prepare several repositories with optional branches before its setup script runs. A blank branch uses the repository's default branch. New copies refresh the checkout; continuing a conversation preserves its current branch and edits.

Add a GitHub trigger to a routine to select an installation, repository, event, sender and conditions. Available families include issues, pull requests, reviews, comments, pushes, branches and tags, workflows, checks, project items, releases, discussions and repository activity. Adding or changing the trigger also adds access to its selected installation. Granting access to an unattended agent requires permission to manage agents.

Same conversation groups subsequent events on the same issue or pull request into one conversation. The trigger author remains its authority; the person who opens an issue does not become the agent's identity. Event bodies are external data, including when they contain instructions. See GitHub and Slack triggers for continuation limits and the event editor.

Reconnect or remove access

A disconnected or suspended installation leaves its grants and triggers visible but unusable. Reconnect it from integrations when appropriate; reconnect a personal account separately when its authorization expires or is revoked. Deleting an installation in Standards removes its dependent grants and triggers as well as its connection rows. Existing conversation history stays available under its normal access rules.

Next steps

Prepare environment repositories, or connect Slack to keep the conversation in a channel.

• Book a demo