Read-only links that show the current diagram

What a share link is

A share link is a public URL of the form /s/<token>: a 32-character id stored against the document, one per document. Runic resolves it on the server on every load and renders whatever the text says at that moment, so the link cannot go stale the way a pasted screenshot does.

Both document kinds share the same way. A process opens the read-only flow viewer; a sequence diagram opens the read-only sequence viewer. A token that no longer exists shows 'This link doesn't exist'.

What viewers see

The shared page has a dark header with the document name, a 'Shared · read-only' chip and a 'Try Runic' button. Under it sits the diagram with zoom controls (25% to 250% for a process, 50% to 150% for a sequence diagram), the Flow direction toggle for processes, hover highlighting and an Export menu. There is no editor and no text field.

An open page checks the source every 45 seconds. When the document has moved on, a banner says 'This flow was updated after you opened it.' with a 'Show the latest version' button. Nothing swaps under the reader until they click.

Cross-process links are inert in the shared view. A .go or .do card does not jump to another document, because that document was not shared.

Creating and revoking

Sharing needs a signed-in account, because the link resolves on the server; without one the menu says 'Sharing needs an account — sign in so your flows live on the server.' Creating a link is idempotent: the button returns the existing token if the document already has one, and copies the URL to your clipboard the moment it exists. Pending edits are flushed first, so the link shows what you see.

Revoke deletes the token. The next visit shows 'This link doesn't exist', and any embed built from the same token stops too. Creating a link again mints a fresh token, so old copies of the URL stay dead.

Limits and gotchas

You need write access to the document to create or revoke its link; team viewers are told to ask an editor. Link creation is rate-limited to 60 per hour per account, processes and sequence diagrams together.

A share link is 'anyone with the link', not 'anyone who searches'. Share pages send noindex headers and robots.txt disallows /s/. The same token also serves a public JSON endpoint at /api/shared/<token> with the document's kind, name, text and last-updated time, so treat the URL like the document itself.

How to use it

1. 1
   Open the document

   Pick the process or sequence diagram in the sidebar. The violet Share button sits at the top right of the diagram pane.
2. 2
   Click Share

   The menu opens with the sharing section on top and the Export items underneath.
3. 3
   Click Create share link

   Runic saves pending edits, creates the token, shows the URL in a read-only field and copies it. The note reads 'Copied to your clipboard — paste away. Anyone with the link can view — not edit.'
4. 4
   Paste it anywhere

   Use Copy if you need the URL again. Clicking into the field selects the whole link.
5. 5
   Revoke when the audience changes

   Click Revoke in the same menu. The menu confirms 'Link revoked — it no longer works.'

Commands & shortcuts

Tips

• Reloading the editor resets the menu to 'Create share link', but clicking it again returns the same URL. You only get a new token after Revoke.
• Viewers can flip a process between top-down and left-to-right and export PNG, SVG, text or Markdown from the Export menu on the shared page.
• Sharing a process does not share the processes it calls. Share each one separately if the reader needs to follow the .do and .go lines.
• Ask Claude for the link: the MCP share_document tool creates or returns it without opening the app.

Questions