Diagrams
Have processes, decision trees and schedules drawn — in chat, in Texts and everywhere else.
Kasimir can draw things instead of only describing them: processes, decision trees, schedules, responsibilities. Just ask in chat — the diagram appears fully rendered in the answer, not as source code.
Getting a diagram
No switch, no tool needed. Simply phrase the request:
"Draw the approval process as a flowchart."
"Show the sequence as a sequence diagram, numbered."
"Turn this into an org chart."
"Show the project phases as a Gantt chart."
Kasimir handles the usual kinds: flowchart, sequence, class and state diagram, entity relationship, Gantt, pie chart, mind map and user journey. If you do not name a kind, the model picks a fitting one.
The more specific the request, the more useful the picture. Name the participants, the order and the decision points — or point at a document: "Draw the process from page 12 of the manual as a flowchart."
Two examples
This is what a flowchart looks like (this page renders it exactly as chat does):
flowchart LR
A["Request arrives"] --> B{"Below EUR 5,000?"}
B -->|"yes"| C["Team lead approves"]
B -->|"no"| D["Management approves"]
C --> E["Finance pays out"]
D --> E
E --> F["Filed in the project folder"]And a sequence diagram, showing a process across participants:
sequenceDiagram autonumber actor U as User participant K as Kasimir participant D as Knowledge U->>K: Question about plinth height K->>D: Search company documents D-->>K: three hits with page numbers K-->>U: answer with sources Note over U,K: Clicking a source jumps<br/>to the cited passage
Where diagrams appear
Everywhere Kasimir renders formatted text:
Place | What that means |
|---|---|
Chat | in every answer; still there after a reload, because the diagram is part of the message |
Meetings | in the summary, in generated templates and in "Ask AI" |
Workflows | in the result of a step |
Support tickets | in messages, including the Kasimir team view |
Shared chats | for recipients without an account, too |
Texts | as a dedicated diagram block, editable there |
This documentation | as on this page |
What you can do with a diagram
A toolbar sits above the drawing:
Button | Effect |
|---|---|
Zoom in / Zoom out / Reset view | zoom; the mouse wheel works too |
Fullscreen | view the diagram full screen |
As image (PNG) | download a raster image, e.g. for slides |
As vector (SVG) | scales losslessly, e.g. for print |
As Mermaid file | source as .mmd — to reuse the diagram elsewhere |
Copy source | Mermaid code to the clipboard |
Open as Text | moves the diagram into a Text, where you can edit it |
Editing diagrams
Chat answers are immutable — the history should stay what was said. To edit, use Open as Text: the diagram moves into a Text (the Texts module) and gets its own title including the time.
There it lives as a diagram block with a toggle:
Preview shows the rendered picture.
Source shows the Mermaid code for editing — the preview follows shortly after you type.
Changes run through the same mechanics as any Text: auto-save and version history. So you can experiment safely and return to an earlier state. Exporting as DOCX embeds the diagram as an image.
When the syntax is wrong
Models occasionally slip. You then get no empty box but a notice "Invalid Mermaid syntax" with the source and a copy button. The simplest fix: ask Kasimir to correct it ("The diagram syntax is invalid, please fix it."). The source stays visible, so nothing is lost.
Good to know
While Kasimir is writing, the diagram appears only once it is complete — no flicker, no half picture.
Switching between light and dark mode re-renders existing diagrams without a reload.
On a phone the diagram is fully visible and the page stays scrollable.
Pages without a diagram never load the drawing library — it costs nothing when you do not need it.
Diagrams are produced and drawn in the browser. Nothing leaves the platform for that.