What a line becomes
A line with no leading dot is a step: a white card wired to the card above it. Runic picks the icon from the words — press, click or submit gives a pointer; enter, type or fill an input glyph; mail, send or notify an envelope; verify, confirm or approve a check. Click the icon (“Change icon”) to choose another: type in “Search icons…” to browse the Lucide set, up to 98 matches per query, or click “Auto-detect” to drop your override. Overrides are kept per document and line: signed in, in your browser once Preferences are allowed in the cookie dialog; in the guest editor, with the rest of its local documents. Blank lines are ignored and a Start pill heads every flow.
A line that starts with a dot must be one of ten commands: .if, .then, .end, .go, .do, .input, .wait, .back, .note and .fail. Any other dot-word turns pink and is skipped. Type a dot at the start of a line and the menu lists all ten with a one-line description; the command menu page has the scaffolds and keys.
Decisions are indentation
.if asks the question. Each .then is one answer, indented two spaces under the .if; that branch's steps go two more. Any line directly under an .if before its first .then is an error, and so is a second .if directly under an open .if. Press Enter at the end of an .if line that has no .then under it yet and Runic scaffolds .then Yes and .then No with the caret inside the first branch.
The .then label becomes the chip on the branch arrow: yes, true or evet is green; no, false, hayır or hayir is red; anything else is violet. The match ignores case and surrounding spaces. A .then with no label shows '…'. An empty branch shows a dashed 'Add a step…' slot; an empty question shows 'Type a condition…' in italics. .end at the .if's own indent closes it and the branches merge into whatever comes next. An .end deeper inside a branch draws an End pill on that path only; at the top level it ends the whole flow.
Jumps, calls, inputs, waits, failures
.go names another document and stops this path — a 'Go to' card you click to open it. .do calls another document and continues on the next line — a 'Do' card, also clickable. Both may name a process or a sequence diagram; the menu lists your other documents of either kind as you type, and a name nothing answers to gets an amber band with a '+ Create as process' chip. An empty .go or .do targets 'Untitled'. .input marks where data enters: an 'Input' card with a small field drawn on it. .wait is a pause for time or an event; its card may stay blank. .fail records a failure outcome as a 'Fail' card and the path continues — the lines under it are the recovery. The audit flags lines after a .go or .end on the same path as unreachable.
Captions, return arrows, notes
End a line with a colon and a caption to label its outgoing arrow: 'Customer pays: payment confirmed'. The colon needs a space on at least one side, so https://runicflow.ai and 14:30 stay ordinary text. Captions work on plain steps, .input, .wait, .fail, .do and .back and ride the arrow into whatever box comes next; they tint violet in the editor. On an .if line a caption is an error — branch arrows are labeled by .then. A .go takes no caption: its path ends at the card, and the parser keeps everything after .go as the name.
.back names any other step by a few words of its text and draws a dashed arrow from the box above it to that step, ignoring case — above for a retry loop, below for a skip ahead to a terminal state. A line whose whole text equals what you typed wins outright; otherwise the first plain step containing the words is used, then the first .input line. Right after a box no card is drawn and the flow continues, so several .back lines stack several arrows off one box; after a decision, a .go, an .end or at the top of the document the .back draws its own card and that path ends. ': caption' labels the return arrow. While the words match nothing, a dashed pill beside the box shows what you have typed so far — 'loop back to…' when it is still empty. .note pins a comment icon beside the previous step; consecutive notes collapse into one icon with a count, and an empty .note reads 'Note'.
Errors and edges
A line the parser cannot place gets a pink background and the sync chip reads 'Check line N' until you fix it; the rest of the diagram still renders. .back only targets plain steps and .input lines, never decisions, .do, .wait or .fail cards. One level of indent is two spaces; Tab inserts them and Shift+Tab removes them, across a whole selection at once. The one exception: while an AI ghost suggestion is showing, Tab accepts the suggestion instead. Names of documents are unique across both kinds, so a .do always has exactly one target; when an older process and sequence diagram share a name, the process is the one that resolves.
How to use it
- Type a stepClick + at the top of the sidebar and choose 'Process flow'. The new process is named 'Untitled N' and starts empty. Type a line such as 'User lands on the login page' and a card appears in the flow pane at once.
- Add a decisionOn a new line type a dot, pick .if from the menu with Enter or Tab, and write the question — Runic has already inserted .then Yes and .then No under it, and the caret sits on the .if line. If you typed the .if line by hand instead, press Enter at its end for the same scaffold, with the caret inside the first branch.
- Fill the branchesType the steps of each branch. Enter after a .then or .if line indents two more spaces for you; Tab and Shift+Tab move the current line, or the whole selection, one level.
- Close and continueType .end at the .if's own indent to merge the branches, then keep writing steps underneath. Picking .end from the menu inserts the line plus a fresh line below it.
- Link other documentsType .go or .do and a few letters of a document name, then choose it from the list — processes and sequence diagrams both appear, diagrams marked 'sequence ·'. Click the resulting 'Go to' or 'Do' card in the flow to open that document.
- Caption an arrow, add a returnAppend ': approved' to a step to label its arrow. Type .back and a few words of the target step — the menu lists the document's steps with their line numbers and whether they sit above or below — and a dashed arrow appears once the words match.
Commands & shortcuts
| plain text | a step card; the icon is picked from the words, click it to change |
| .if question | a Decision card; needs .then branches under it; no caption allowed |
| .then label | one branch, indented two spaces; yes/true/evet green, no/false/hayır red, others violet |
| .end | at the .if's indent: close it and merge; deeper or at top level: an End pill |
| .go Document | 'Go to' card — ends this path; click to open; no caption |
| .do Document: caption | 'Do' card — continues on the next line; click to open |
| .input text | 'Input' card — data enters here |
| .wait text | 'Wait' card — time, approval or an event |
| .fail text | 'Fail' card — an outcome; the path continues |
| .back step words: caption | dashed arrow from the box above to the matching step; exact text wins, else first containing |
| .note text | comment icon pinned beside the previous step |
| step: caption | labels the outgoing arrow; the colon needs a space beside it |
| . at line start | opens the command menu — ↑ ↓ move, Enter or Tab inserts, Esc closes |
| Enter after .if | scaffolds .then Yes and .then No when no .then follows yet |
| Tab / Shift+Tab | indent or outdent by two spaces, whole selection included |
Tips
- Put the question in the .if and the answers in the .then labels — a menu with five options is one .if with five .then lines, not five decisions.
- Use .do for anything you will reuse (verification, payment) and .go only when this flow really ends there.
- A state machine is steps with captions plus .back lines: 'created: request shipment', 'shipping', 'delivered', then '.back created: cancel order'.
- Leave a .wait or .input blank while you think; the card renders with only its type label until you fill it.
- If the chip says 'Check line N', look for any line directly under an .if before its first .then, a caption on an .if line, a .then with no .if above it, a second .if directly under an open one, or a dot-word that is not a command.
- Write Turkish flows as they come: .then Evet and .then Hayır get the same green and red chips as Yes and No.
Questions
Does a decision have to be Yes and No?
No. Any label works and any number of branches — the scaffold offers Yes and No because they are the common case. Yes/true/evet and No/false/hayır get green and red chips; every other label is violet. A decision with a single branch still renders, but the audit warns about it.
Can I put a caption on a .go line?
No. The path ends at the Go card, so there is no outgoing arrow to label, and the parser keeps everything after .go as the card's name — '.go Ship: next day' draws a card reading 'Ship: next day' and clicking it looks for a document with that whole name, while the reference index reads the same line as a call to 'Ship'. Caption the step before it instead; its caption rides the arrow into the 'Go to' card.
What does .back match?
A plain step or .input line anywhere in the document, ignoring case. If a line's whole text equals your words it is the target; otherwise the first plain step containing them, then the first .input line. It can be above or below the .back line. Decisions, .do, .wait and .fail cards cannot be targets.
Is there a hands-on tutorial?
Yes. Learn in the account menu opens /learn in a new tab: the real editor with a coach panel and ten steps — a first step, a few more, a decision with two branches, .wait and .input, a .fail with a recovery line, a note, a .do or .go, a caption, a .back, and an edit in the middle — each checked live as you type, with 'Stuck? Show me an example' and a 'Type it in for me' button. It needs a signed-in account; the tour document is not saved.
Where is the full reference?
The Commands section of the docs lists every command with a tested example, and the MCP tool get_syntax_guide returns the same rules as a compact legend for AI clients.