diAIgram

diAIgram writes a diagram for you. Describe what you want in plain English and it produces Mermaid or PlantUML source you can drop straight into the editor. It lives in the diagram tool — look for the button with the rainbow ring.

It is a shortcut, not a replacement. Everything it produces is ordinary diagram source you can read, edit and keep, and nothing about writing a diagram by hand has changed.

Using it#

You need a confirmed account, because generations cost credits and credits belong to an account. Signed out, the dialog explains that and offers you a link to sign in.

Open the dialog and it asks up to three questions:

1. New or modify? — only if you already have a diagram open. Choosing modify skips straight to the last step and applies your changes to what's in the editor.
2. Which syntax? — Mermaid or PlantUML.
3. What kind of diagram? — flowchart, sequence, class, state, ER, Gantt, pie, mindmap or git graph. Pick Something else and it will choose for you.

The first two questions are answered by buttons, not by the AI — they're a fixed list, so there is nothing to get wrong and nothing to pay for. Only the last step, where you describe what you want, involves a model.

Then describe your diagram. Press Enter to send, Shift + Enter for a new line. When the result comes back you can insert it into the editor, or start over.

Writing a good description#

The model only knows what you tell it. A description that names the steps and how they connect gets a much better diagram than a topic.

Instead of "a login flow", try:

A user signs up and we email them a verification link. If they click it within an hour their account is active; if it expires they can request a new one. An unverified account is deleted after seven days.

Worth knowing:

• Name the decisions. "If X then Y, otherwise Z" becomes a branch. Without it you get a straight line.
• Keep labels short. Long node text makes a wide, awkward diagram — that's a property of the layout engine, not of the model.
• Iterate. Generating, inserting, then asking for a change is usually faster than describing everything perfectly first time.
• Descriptions are capped at 2,000 characters, which is a lot of detail — roughly 300 words.

Credits#

Each generation costs between 1 and 10 credits, depending on how much work it took: the length of your description, the diagram it had to hold in mind, and the size of what it wrote. A small flowchart is at the bottom of that range; a large sequence diagram with many participants is nearer the top.

New accounts start with 200 credits. Your balance is shown at the top of the dialog and updates as you go.

Credits cannot be bought yet. While diAIgram is in preview there is no top-up and no paid tier — the grant is what you have. If you run out and have a reason to need more, ask: the Buy more button in the dialog opens a contact form where you can request additional credits.

A generation that fails costs you nothing. If the model returns something that isn't a diagram, or the request times out, no credits are taken.

What it can't do#

• It can't see your diagram render. It writes source; whether that source draws well is something only you can judge. If a diagram comes out cluttered, ask for it again with fewer elements.
• It doesn't know anything after its training. Ask it to diagram a recent release and it will invent the details.
• It isn't a chat assistant. It answers with diagrams. Asking it questions will get you a diagram of your question.
• PlantUML gets less practice. Both engines work, but Mermaid is the better-trodden path and its output is generally more reliable.

Privacy#

Your descriptions and the diagrams generated from them are sent to the model provider to be processed, and stored on mdbin for 30 days so you can come back to them — the Recent list in the dialog is that history. After 30 days they're deleted.

Nothing generated is published. A diagram exists only in your editor until you choose to save or publish it, exactly like one you typed yourself.

Using AI from an agent instead#

If you're a coding agent reading this: diAIgram is a browser feature and there is no tool for it. You don't need one. Write Mermaid or PlantUML directly into a ```mermaid fence and publish it with create_document — you're already generating the source that this dialog exists to produce for people who aren't. See MCP for agents.