Docs
An agent may suggest. It may not overwrite.
Agent edits to a shared document arrive as suggestions, rendered as inline diff with accept and reject in the margin. The document never changes underneath the person reading it.
How it answers to the conversation
The decision and the document it changed, in one place.
A doc updated by an agent posts an artifact card carrying the shape of the change. Accepting a suggestion writes back to the card, so the channel records who decided what.
Inline suggestion diff
Green and red in the body of the document, with accept and reject controls in the margin. Nothing merges silently.
Mixed contributors
The contributor list shows people and agents together, because both wrote it and both should be visible.
Open questions
A checklist that survives the document. Struck-through items keep their answer, so nobody relitigates a settled question.
On this page
A structural rail, not a table of contents someone maintains by hand.
What it does
Three things this surface is for.
Human authority, enforced
Suggestion-only is not a setting an agent can turn off. It is how the surface works, and it is why a team will let agents near its docs.
Docs that know the work
The document lives in the channel that produced the decision, so an agent writing it has the diff, the test and the thread to hand.
Nothing is lost
Version history and per-block attribution. Rejecting a suggestion keeps the suggestion in the history.
Yours or ours
Write them here, or keep them in Notion.
Already have years of pages in Notion? Connect it. The pages stay in Notion, open in the channel, and agents suggest edits to them the same way — as suggestions you accept or reject.
| Surface | Built in | Connect instead |
|---|---|---|
| Docs | Included |
|
Where it appears
Channels that expose this surface.
Planning, research and incident channels get docs. So do feature channels, because a decision worth making is worth writing down.
- Docs A document an agent may suggest edits to, and a human accepts them. Built in, or connect Notion, Google Docs
- Diagrams A canvas a person and an agent draw on at the same time. Built in, or connect Figma, Miro
- Issues An issue filed from the channel that produced it, assigned to an agent. Built in, or connect Linear, Jira
- Roadmap Periods and lanes, where each item groups the issues that deliver it. Built in, or connect ProductBoard
Division of labour
What agents do here, and what needs a person.
Agents draft
A first pass from the thread that produced it — the decision, the options that lost, and the reason.
Agents keep it current
When the code moves, the agent proposes the doc change. It arrives as a suggestion like any other.
A person accepts
Every word that lands in a shared document passed a human. That is the whole design, on this surface and on Review.
Let agents write the docs. Keep the last word.
Crusible is opening to teams in private beta.