Diagrams
Two cursors on one canvas, and one of them is not a person.
Architecture arguments get settled in boxes and arrows. Diagrams puts that canvas inside the channel, with agents drawing on it beside you rather than describing what they would draw.
How it answers to the conversation
The picture and the argument stay together.
A canvas that lives in a separate tool loses its context the moment the discussion moves on. This one is attached to the channel that produced it.
Live presence
Named cursors for everyone on the canvas, human and agent alike, at the same size and with the same weight.
Author attribution
Hover any element to see who put it there. An agent's boxes are identifiable without being second class.
Artifact card
A canvas posts into the conversation as a card with a live thumbnail, so a reader knows whether to open it.
Version history
Every state of the canvas is recoverable, which is what makes it safe to let an agent rearrange it.
What it does
Three things this surface is for.
Draw the system
Boxes, edges, stickies and frames. Enough to argue about an architecture, not a general-purpose illustration tool.
Agents draw too
An agent that has read the codebase can lay out what is actually there, which is usually the hard part of the diagram.
It becomes a doc
A settled canvas embeds into the Docs surface in the same channel, under the decision it illustrates.
Yours or ours
Draw here, or keep the board in Figma.
Your team already lives in Figma or Miro? Connect it. The board stays yours, opens in the channel, and the channel does not change shape.
| Surface | Built in | Connect instead |
|---|---|---|
| Diagrams | Included |
|
Where it appears
Channels that expose this surface.
Planning and research channels are built around it. Feature and incident channels get one when someone opens a canvas.
- 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
- Design preview The running component, not a picture of it. Built in, or connect Figma
- 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 map what exists
Read the repository, draw the real call graph or the real service topology. Tedious for a person, quick for an agent.
Agents keep it honest
When the code diverges from the picture, the agent flags the elements that no longer match.
A person decides the shape
What the system should look like is a design judgement. The agent renders options; it does not pick.
Argue in boxes and arrows, together.
Crusible is opening to teams in private beta.