What it is
The editor is a plain textarea over a syntax-colored layer. The visual flow on the right is not a second document: it is computed from the text on every render by parsing the lines and running the layout engine. Nothing is stored for the diagram, so nothing can drift.
That is why the pane header reads “Visual flow · Generated from text · read-only”. You cannot drag a box, and you never need to. The text is the only source of truth.
How it works
On every change the app calls parse() on the document and buildFlow() on the result, with a canvas-backed measurer so card heights match how the browser wraps the words. The layout is a pure function of the text: the same document always draws the same picture.
Cards carry a 0.35s transition on position, so a new line pushes the boxes below it down in a glide. Lines that did not exist a moment ago are found by a line diff and their nodes scale in at their final spot over 300 ms instead of sliding from a sibling’s old one. Reduced-motion settings turn both off.
Hover works both ways. Hover a line and its node rings violet and the diagram scrolls to keep it in view; hover a node and the editor highlights and scrolls to its line. The editor also tints the caret line, error lines (pink), broken-reference lines (amber) and draws a faint guide at every two-space indent level.
The sync chip
The chip in the editor header has five states. “In sync”, green with a pulsing dot, means the text parses and is saved. “Saving…” shows while a save is in flight. “Offline — retrying”, amber, means the last save failed; Runic keeps the unsaved text and retries every 3 seconds until it lands. “Check line N”, amber, means a line cannot be parsed and names the first one; it overrides the save state until the line is fixed. “View only” replaces all of them on a team document where your role is viewer.
Signed in, text and name changes are batched and sent 600 ms after your last keystroke. The footer under the editor counts the lines; take the save state from the chip, not the footer.
Why it matters
Mid-flow edits are the point. Inserting a step between two others is one Enter and one sentence; the diagram reflows around it. Mistakes surface as you make them: a line the parser cannot place tints pink and the sync chip switches from “In sync” to “Check line N”.
Limits
Rendering runs on the main thread with no debounce. The grow-in animation is skipped when more than 30 lines arrive at once, such as a large paste or an AI draft. Before the first line the canvas reads “Nothing to draw yet — Describe the first step in the editor and the flow will appear here as you type.” The sequence pane has the same live behaviour with its own parser and its own empty state.
How to use it
- Type a stepWrite a sentence on its own line. A card appears under Start before you finish typing it.
- Insert in the middlePut the caret at the end of any line and press Enter. The new line keeps the indent above it; the boxes below glide down.
- Watch the sync chipThe header pill reads “In sync” while the document parses and is saved, “Saving…” or “Offline — retrying” around a save, and “Check line N” when a line cannot be placed.
- Hover to locateHover a line and its node rings violet; hover a card and the editor scrolls to its line.
- Change an iconClick the icon on a step card (“Change icon”). Type in “Search icons…” to pick from the Lucide set — the picker shows up to 98 matches at a time and says “First 98 of N” when there are more — or click “Auto-detect” to go back to the icon Runic picks from the words.
- ZoomUse − and + in the toolbar, hold Ctrl or ⌘ and scroll, or click the percentage to type a value. Zoom runs from 25% to 250%.
Commands & shortcuts
| Enter | New line at the same indent; two spaces deeper after .then or .if |
| Ctrl / ⌘ + scroll | Zoom the diagram toward the cursor (trackpad pinch works too) |
| Click the % readout | Type a zoom level; Enter commits, Esc cancels |
| In sync · Saving… · Offline — retrying | Sync chip save states; failed saves retry every 3 s |
| “Check line N” | Sync chip state when a line fails to parse |
| Click a step icon | Icon picker: search, up to 98 results per query, “Auto-detect” removes your override |
Tips
- Each line is one card. Long sentences wrap inside the card rather than widening it, so keep steps short and put detail in a .note.
- The caret line’s number turns violet in the gutter. Use it to find yourself after a long scroll.
- Signed in, icon overrides are remembered per document and line once you have allowed Preferences in the cookie dialog, and last for the session without that consent; the guest “Try it” editor keeps them with the rest of its local documents.
- Fullscreen the diagram with the Fullscreen button in the toolbar when presenting; Esc brings the panes back. The account menu’s Dark mode switches the whole editor to a navy palette.
- Reduced-motion settings in your OS turn off the glide and grow-in animations.
Questions
Is there a save-and-render step?
No. Parsing and layout happen inside the same render as the keystroke. Saving is separate and automatic; the sync chip shows “Saving…” and “In sync”, or “Offline — retrying” when the server cannot be reached.
Can I move a box in the diagram?
No. Positions come from the text and the layout engine. To move a step, move its line: drag the ⋮⋮ handle or cut and paste.
Why did a line turn pink?
The parser could not place that line, usually a .then outside an .if, a step directly under an .if before its first .then, or an unknown dot-word. No card is drawn for it until it parses, and the sync chip names the first bad line.
What does “View only” mean?
You opened a team document as a viewer. The diagram renders and exports, but the text cannot be changed, so the chip reports that instead of a save state.