GitHub

Connecting GitHub gives Introspection access to your repositories: the source of truth for your agents’ behavior, and the place agent work lands as pull requests.

GitHub is connected once per organization, from the organization integrations page in the app. Rather than a plain OAuth token, the connection uses the Introspection GitHub App: you install it on your GitHub account or organization and pick which repositories it can access. The connection is org-scoped (one live GitHub connection per organization) and the credential is stored encrypted.

What it enables

Recipes pinned to commits

A recipe is a precise pointer into git: a repository, a ref, a commit SHA, and an optional sub-path. Connecting GitHub makes your repositories available as recipe sources, so you can pin a runtime’s behavior to an exact commit. Because every recipe is pinned to a commit, every run stays reproducible.

Pull requests from agent tasks

Agent tasks can open pull requests against a connected repository, the typical way a coding agent proposes a change. The work runs in the task’s sandbox, and the result is a PR you review and merge like any other.

Repository access for runs

When a task needs your code, the platform mints a short-lived installation token from the GitHub App and uses it to clone the repository into the run’s sandbox. Tokens are minted per-use, never long-stored.

Webhooks are handled by the platform

GitHub sends Introspection events about your installation (when the App is installed, suspended, unsuspended, or uninstalled) and about pull requests. These webhooks are received and verified by Introspection’s control plane directly.

The platform uses them to keep the connection’s state accurate:

If you suspend or uninstall the App from GitHub’s own UI, the connection is reflected as disabled or removed on the Introspection side.
When a pull request opened by an agent task is closed or merged, the originating task is updated to match.

Because lifecycle events flow back from GitHub, the connection stays in sync whether you manage it from Introspection or from GitHub. Disconnecting in the app also uninstalls the App on GitHub.

Connecting and disconnecting

Connect: an admin or owner installs the Introspection GitHub App from the organization integrations page and selects the repositories to grant.
Disconnect: removing the connection in the app uninstalls the App installation on GitHub and revokes Introspection’s access.

If GitHub later reports that an installation has expired or been revoked, the connection is flagged so an admin can reconnect.

Recipes: how a repository and commit become your agent’s pinned behavior.
Tasks: the executions that open pull requests.
Integrations overview: the integrations you can connect to your organization.