34 FEATURES · 6 AREAS

Everything Runic does, one page each.

Runic is a text editor with a whiteboard attached: you write a process as plain lines, a flowchart or sequence diagram builds itself beside you, and an AI agent edits the text with diffs you review. Each page below explains one capability in full — what it does, how to use it, and where it stops.

The editor

What the editor does for you because your process is text — and no canvas tool can copy.

LIVE

The diagram redraws on every keystroke

Every change to the text re-parses the document and rebuilds the flowchart in the same render. Nodes glide to their new positions, brand-new steps grow in at their spot, and hovering either pane lights up the twin in the other.

EXTRACT

Select steps, convert them to a process

Select two or more lines and a floating bar offers “Convert to process”. Name it, press Enter, and the block leaves the document as its own process while a .do line stays behind. Half a decision can never be extracted: the selection grows to keep every .if with its branches.

REFERENCES

See every flow that calls this one

Runic indexes every .go and .do in your workspace. The sidebar shows a badge with the number of call sites in other processes, the References panel lists each call site with a line preview, and one click jumps to that line in that document.

RENAME

Rename once, every reference follows

Click the document name, type a new one, press Enter. Runic rewrites every .go and .do line that targeted the old name in every process you can edit, keeping indentation and the command intact. A rename cannot quietly break a flow you forgot about.

AUTOCOMPLETE

It knows your commands and your process names

A dot at the start of a line opens the Commands menu. After .go or .do the menu lists your other processes; after .back it lists the steps of the current document. Arrow keys move, Enter or Tab inserts, Esc dismisses, and typos stop being a category of problem.

FOLDING

Collapse what you are not reading

A chevron appears in the gutter beside any line with indented lines beneath it. Click it and the block collapses to a “⋯ N lines” chip. The fold is a view: the document is untouched, the diagram is complete, and the first edit or click expands everything with the caret exactly where you aimed.

QUICK FIX

A link to nowhere fixes itself

A .go or .do whose target does not exist gets an amber band and an inline “+ Create as process” chip. Click it and Runic creates the process with exactly that name and opens it. The sidebar shows an amber dot on any document that still has a broken link.

REORDER

Move a block, the picture follows

Hover a line and a ⋮⋮ handle appears. Drag it and the line moves with every deeper-indented line under it, plus the closing .end of a decision; the block re-indents to fit where it lands. Select several lines and they move as one. Tab and Shift+Tab shift every selected line by one level.

NOTES

Notes that do not cover the diagram

Write `.note` under any step to attach context, ownership, or an edge case. In the diagram the note becomes a yellow comment icon beside the card; several notes on one step collapse into a single icon with a count badge. Image exports show the full text.

LAYOUT

One text, laid out your way

The layout engine turns the parsed text into positions. Four toolbar toggles shape the result: direction, compact cards, branch alignment and tight packing. Arrow captions come from a colon on the line. Return arrows are routed through clear gutters so they never cross a box.

KEYS

Every shortcut Runic binds

Runic keeps its shortcuts few and predictable. The process editor owns undo and redo, Tab and Enter do structural work, Esc closes the nearest thing, and Enter sends a chat message. This page lists what each key does and where.

The AI agent

An agent that edits documents the way a careful colleague would: proposals wait as diffs, every change is a checkpoint.

AI CHAT

Tell the agent what to change. Review the diff.

The chat panel beside the editor proposes changes as green-and-red diffs of your document. Nothing is written until you click Apply, every applied change keeps a checkpoint, and each request runs on the model that fits it: Sonnet for ordinary turns, Opus for whole-document work.

CHECKPOINTS

Every applied change keeps a way back

When you apply a proposal, Runic keeps the full text of the document before the change on that chat entry. Click ↩ Restore, even much later, to return to it. Checkpoints are keyed to the document’s id, so they survive renames, reorders and archiving.

LIVE PREVIEW

See the proposal as a diagram before you accept it

A pending proposal renders in the flow pane as the diagram it would produce, with added or moved steps highlighted in green and a banner offering Apply and Discard. The editor keeps showing your current text, so you judge the change the way you think about it — as the flowchart.

SELECTION

Point the agent at exact lines

Select lines in the text or draw a box over nodes in the diagram, then press Copy to chat. A chip pins the range to your next message, and the reply is a diff confined to those lines by construction: the model returns only the replacement, and Runic splices it into the same range.

AUDIT

Two audits in one click: structure, then meaning

One button under the chat runs a deterministic structural pass — one-branch decisions, empty branches, unreachable steps — and then hands the document to an AI analyst who reads it for missing failure paths, unclear roles and domain gaps. The same structural check runs on its own after every change the AI writes.

MEMORY

The conversation follows your account

The chat is saved with your account, not your browser. Long conversations fold older messages behind short summaries the agent still sees, and when you refer back to something specific, the original messages are recalled verbatim. Say “apply what you suggested” and it knows what you mean.

GENERATE

Describe an operation, get a linked set of processes

Describe a narrow flow and Create with AI writes one process. Describe a whole operation — stages owned by different people or systems — and it writes a system: a main flow that calls two to six sub-processes, every reference checked against the set, every document run through the structural repair pass, then placed in your sidebar as a nested tree.

QUESTIONS

After the draft, the agent asks what it left open

A generated system is the happy path. Runic reads it back and queues the questions whose answers would change the diagram — validations, thresholds, failure handling, permissions — then asks them one by one in the chat. Each answer becomes a proposal on the process the question was about.

IMPORT

Import a whiteboard photo or a Mermaid file

Attach a photo of a whiteboard, a screenshot of a flowchart or a Mermaid file to a chat message. The agent reads every node, edge label and branch, translates them into Runic syntax, and either creates a new document or proposes a merge into the open one as a reviewable diff.

Build handoff

Shape the idea here, then hand your AI tools a complete spec instead of a guess.

PACKAGE

Everything Claude Code needs, in one zip

The Build Package turns the processes you tick into a developer-ready folder. The AI writes one structured spec object; Runic renders every file from fixed templates, so the shape of the zip never depends on the model. Unzip it into an empty repo and Claude Code has the spec, the plan and your flows as source.

INTERVIEW

Up to eight questions before the spec

A flow says what happens. It rarely says who may do it, what data each step reads or writes, or what failure looks like. The build interview pulls that out of your head in up to eight questions written for these flows, and folds the answers into docs/spec.md. Unanswered questions are listed as open questions rather than guessed.

HANDOFF

One prompt: read the spec, plan Milestone 1, wait

The handoff is two files working together. KICKOFF.md is the prompt you paste; CLAUDE.md is what Claude Code keeps reading afterwards. Together they make the spec binding, the flows the source of truth, and your approval the gate before code exists.

The language

Ten single-word commands for flows, a handful of arrows for sequences. Indentation carries the structure.

PROCESS

Ten commands, one node per line

Every non-blank line in a process document becomes something in the flowchart: a card, a branch, an arrow or a note. Plain text is a step; ten dot-commands add decisions, branches, ends, jumps, sub-processes, inputs, waits, failures, return arrows and notes. Indentation decides how they connect, so there is nothing to draw.

SEQUENCE

Sequence diagrams from arrows you type

A second document type for who-talks-to-whom. Each line is one message between two actors — solid for requests, dashed for replies — with .loop and .alt/.else blocks for repetition and branching. Actors appear in the order you first mention them, or the order you pin with .actor.

Platform & account

Sign-in, MCP for Claude, and the privacy choices that shaped how Runic is built.

MCP

Connect Claude to your flows over MCP

Runic ships a Streamable HTTP MCP server at /api/mcp with 11 tools. Create a token from the Claude & MCP modal, add one line to Claude Code, and Claude can list, read, write, audit, share and roll back your flows. It learns the Runic language from the server's own syntax guide.

SIGN IN

Sign in with email, Google or GitHub

Runic accounts use email and password, Google or GitHub. Providers link to one account by verified email, the Connected accounts modal adds or removes them without ever removing your last way in, and a password reset link works once and expires in two hours. Sessions are a 30-day httpOnly cookie.

PRIVACY

Three cookies, no trackers, your data on request

Runic is built to hold as little as possible: a session cookie, a ten-minute OAuth state cookie and the cookie that records your consent choice, self-hosted fonts, a Content Security Policy that only allows connections to Runic's own origin, and AI calls that leave the server only when you invoke a feature. Download my data returns everything as JSON; Delete account… erases it after a password check.

Read enough. Try it.

A free account takes a minute. Write three lines and watch the diagram appear.

Create a free account →Read the docs