How it answers to the conversation
Artifact card in, surface out, card back.
An agent opens a pull request. What lands in the transcript is a card, not a paste — enough to answer "do I need to look?" and a doorway if you do.
The card
Changed-file count, CI state, reviewer states, and the branch. Compact enough that the transcript stays scannable.
The surface
Opening it takes the centre. The full diff, the job bars and the review threads, with the conversation one gesture away.
The way back
Every review action writes back to the card, so someone reading the channel a week later sees what happened without opening anything.
The gate
Where a merge needs a person, that stop is part of the plan the agents run — not a pop-up bolted on at the end.
What it does
Three things this surface is for.
An agent as a reviewer
Listed alongside the humans, with its own state, its own permissions and its own cost line. Not a bot comment — a reviewer.
CI where the diff is
Job bars beside the changed files, and a failing job that promotes itself into the conversation if it crosses the threshold you set.
Merge rights are explicit
"May merge without a human" is a per-channel permission on an agent, visible in the roster and in the audit log.
Yours or ours
Your git host, or ours.
Crusible hosts the repository, or GitHub does, or GitLab does. Either way nothing above the surface changes — same channel, same conversation, same agents, same permissions.
| Surface | Built in | Connect instead |
|---|---|---|
| Review | Included |
|
Where it appears
Channels that expose this surface.
Worktree and feature channels get Review. An analytics channel has nothing to merge, so it does not.
- Terminal A shell on a worktree, in the channel that needs it. Built in
- Project Mounted repositories, a file tree, and the diff that matters. Built in
- Review A pull request opens in the channel that produced it. Built in, or connect GitHub, GitLab
- Flow Agents, CI jobs, a human gate and a deploy — peers in one graph. Built in
Division of labour
What agents do here, and what needs a person.
Agents open and revise
Draft the change, respond to review comments, rerun the checks, push the fixup. All of it inside the channel that asked for the work.
Agents review
A review discipline reads the diff against the channel's own context — the decision, the failing test, the incident that started it.
A person decides
Merge to a protected branch, anything touching production, and any change an agent's permission set does not cover. The gate is a node, not a nag.
How it is put together
- 1:1 Pull request to channel — every one has a homeRFC-0025 §6
- 2 Git hosts connectable, plus Crusible's ownRFC-0029 §5
- 0 Merges to a protected branch without an explicit permissionRFC-0020 §6
Review where the work happened.
Crusible is opening to teams in private beta.
