Runic
RENAME

Rename once, every reference follows

Change a document name in the top bar and every .go and .do that points at it is rewritten across all your documents.

Try it free →Read the docs

What it is

Document names are the symbols of your workspace: .do Verify payment is a call and “Verify payment” is its definition. Runic treats a rename the way a code editor treats rename-symbol: one edit, every call site updated.

How it works

The document name in the top bar is click-to-edit; hover shows a dashed underline and the tooltip “Rename document”. Enter commits, Esc restores the old name, clicking away commits. Names are capped at 80 characters. The sidebar has no rename control; the top bar is the one place.

On commit the new name is first made unique across every document of both kinds: if “Manager approval” already exists, you get “Manager approval 2”. Then Runic scans every document you can edit, processes and sequence diagrams, for .go <old name> and .do <old name> lines, case-insensitive and trimmed, and swaps in the new name. Indentation, the command and an arrow caption stay as they were: .do Ship: next day becomes .do Dispatch: next day. Each changed document is saved by the normal autosave, so the rename reaches the server as ordinary text edits, and the badges, nesting and autocomplete reflect it at once.

Why it matters

Names drift as a process matures: “Approve request” becomes “Manager approval”, then “Line-manager approval”. Without propagation each rename is a search across every document and a chance to miss one. With it, the name is free to improve.

Limits

Propagation runs in the editor. A rename through the MCP server changes only the name, as the rename_document tool description says; run the app’s rename, or check the references tool afterward. Documents you can only view are skipped. If another document still answers to the old name after the rename — a process that shadows a same-named sequence diagram — nothing is rewritten, because those call sites still resolve.

How to use it

  1. Click the name
    In the top bar, next to the Runic logo, click the current document name. It becomes an input holding the current name.
  2. Type the new name
    Up to 80 characters. Spaces and punctuation are fine; matching is case-insensitive.
  3. Press Enter
    The name commits, made unique with a “ 2” suffix if it was taken. Every .go and .do line in your other documents that targeted the old name is rewritten to the new one. Esc cancels instead.
  4. Check the sidebar
    The row shows its new name and keeps its reference badge; nested rows stay nested.
  5. Verify a call site
    Click the reference badge to list callers and confirm the lines now read the new name.

Commands & shortcuts

Click the document nameTop bar, tooltip “Rename document”; the input takes 80 characters
EnterCommit the rename and propagate
EscCancel and keep the old name
“Name 2”What you get when the new name is already taken by any document
rename_document (MCP)Changes only the name; no reference rewriting

Tips

  • Open the References panel before renaming if you want to see exactly which lines will change.
  • The rewritten call sites are not on the undo stack, so ⌘Z will not put the old name back. To reverse a rename, rename the document back; the references follow again.
  • Viewer-role team documents are left alone. Ask an editor to update those call sites.
  • Captions survive: a call like .do Verify payment: same day keeps “: same day” and gets the new name in front of it.

Questions

Which documents get rewritten?

Every process and sequence diagram in your workspace that you can edit and that contains a .go or .do targeting the old name. Team documents where your role is viewer are skipped.

Does rename touch plain-text mentions?

No. Only lines that start with .go or .do and whose target equals the old name are rewritten. A step that happens to mention the name in prose is untouched.

What about references with captions?

They are rewritten too. The caption is not part of the target, so .do Ship: next day is recognised as a call to “Ship” and becomes .do Dispatch: next day when Ship is renamed to Dispatch.

Can two documents have the same name?

Not through rename or create: Runic appends a number. Documents that already shared a name before this rule resolve to the process first, then to the earlier document in the list.