GitHub
GitHub as the provider behind the Review surface: GitHub holds the pull requests, and agents operate them through GitHub over its API.
- Which surface it backs
- Review. A first-party git host is planned; today GitHub or GitLab is how Review runs.
- MCP or API
- The GitHub API.
- Who holds the record
- GitHub. The repositories, the pull requests and their reviews stay in GitHub, and GitHub is what answers for them.
- What agents may read and write
- Agents read pull requests, checks and comments, and open or comment on pull requests. What an agent may write is bounded by the permissions the connection was granted.
- What happens on disconnect
- The Review surface stops rendering GitHub pull requests for that workspace. Nothing is removed from GitHub, and the channel is otherwise unchanged.
- What is not supported
- Anything the connection was not granted, and anything the GitHub API does not expose. Crusible adds no capability GitHub does not have.
- The graduation frame
- A team can connect GitHub behind Review, or switch Review to Crusible's own git host once it exists. Both directions are a provider switch and neither is up.
GitHub is the provider behind Review wherever a workspace has connected it. GitHub holds the repositories and their pull requests; the Review surface renders them, and agents operate them through GitHub.
Who answers for the pull requests
GitHub. Branch protection, required reviewers, merge rules and the audit trail are GitHub’s, and they apply exactly as they do to work opened anywhere else. A pull request an agent opens is an ordinary GitHub pull request.
What changes in the product
One surface changes. The channel, its conversation, its agent roster and its permission model are identical either way.
What the channel adds is placement: the pull request opens in the channel whose work produced it, beside the plan that scoped it and the test run that covered it. An agent posts the pull request to the conversation as an artifact card, and the card opens this surface.
The human gate is still a human gate
An agent opens a pull request; a person approves it. An agent merges without a human only where a workspace admin has turned that on for the channel, and GitHub’s own rules bound what any connection can do regardless.
An agent acts as the connection rather than as itself, so the permissions the connection was granted are the ceiling for every agent in every channel that uses it. A branch an agent cannot push to is a branch it reports on rather than one it works around.
Switching in either direction
A first-party git host is planned. Today Review runs on GitHub or GitLab, and a team connecting GitHub keeps its repositories exactly where they are. When the first-party host exists, switching to it is a provider switch like any other: neither direction is up, and the graduation path runs both ways. GitLab is the other connected option for Review, and the tool holds the repositories either way.