Sketch it out

You can ask your agent to draw a diagram into the doc. Architecture sketches, sequence diagrams, flowcharts, state machines, anything you'd normally hand-draw on a whiteboard, the agent renders inline next to the prose.

How to ask

Open the chat panel and describe what you want, the more concrete, the better:

Sketch the magic-link auth flow as a sequence diagram, web client, auth service, email queue.
Draw an architecture diagram for our pipeline, three services and a queue between them.
Show the order-status state machine: pending, paid, shipped, delivered, cancelled.

Press ↩.

What you'll see

A short reply lands in the chat ("Drawing it now, sequence diagram going in below"), then the diagram draws into the document below your cursor, with the boxes and arrows appearing one piece at a time.

The diagram is part of the document, it scrolls and exports with the rest of your text. You don't need to manage a separate file or paste an image.

Iterate

If something's off, comment on the diagram (or just ask in chat): "Add a Postgres node off the auth service for token storage" and the agent re-renders with the change.

You can also have multiple diagrams in one doc, ask for each one separately and the agent will drop them where your cursor is.

What kinds of diagrams work

The agent is good at:

Sequence diagrams, request/response flows between systems.
Architecture diagrams, boxes and arrows for services, databases, queues.
Flowcharts, decision branches.
State machines, named states with labeled transitions.

For something pictorial that isn't really a diagram (a logo, a UI mock, a chart of real data), a dedicated tool is going to do better.

Tips

Name the participants. "Browser → Auth → Email" is a much better seed than "the auth flow."
Specify the direction. Top-down or left-right; sequence or component view.
Ask for revisions, not rewrites. "Add a refresh-token arrow back to the client" is faster than re-asking for the whole diagram.