Type // to connect any two files. Backlinks appear automatically, links survive renames, and the whole connected graph is served to your AI tools — not just isolated pages.
One trigger, three forms, zero maintenance
Anywhere in any file, type // and an autocomplete popup appears with your files. Pick one and the link is made — no dialogs, no leaving the keyboard.
Add a pipe to display custom text while linking to the same file. Paths work too when two files share a title.
Reference a page you haven’t written. The link waits as a pending reference and connects itself the moment a file with that title is created — sketch the structure first, fill in pages later.
The // trigger never fires inside https:// URLs, code blocks, inline code, or mid-word. Your snippets stay snippets.
Links resolve by file identity, not text matching. Rename or move a file and every inbound link follows, displaying the new title.
Delete a target and links become visible pending references — recreate the file and they reconnect on their own.
Links stay human-readable in the content itself — //Title, not opaque IDs — so files remain portable and diff-friendly.
Open any file and see everything that references it — the links people made on purpose, and the mentions they didn't. Your knowledge base stops being a pile of pages and becomes a graph.
Files that link here with // — the deliberate connections. Perfect for seeing what depends on a runbook or decision before you change it.
Files that mention this one by name without linking — connections waiting to be made. One click turns a mention into a real link.
Every save is a version — compare, diff, and roll back like Git for docs.
Type #tag anywhere and it becomes an organizing tag, Obsidian-style.
Discuss and resolve threads directly on files.
Full-text search across every library — by you or your AI.
Public share pages render linked files too, with access control on every hop.
The whole graph is served over MCP — your AI follows links between docs the way you do.
Type // anywhere in a file and an autocomplete popup appears — pick the file you want and the link is done. Links look like //Onboarding Guide in the text, and you can give one a custom label with a pipe: //Onboarding Guide|Read this first.
Nothing breaks. Links resolve by file identity, not by matching text — rename or move the target and every link pointing at it keeps working and displays the new title automatically.
Yes. The link is kept as a pending reference, and the moment a file with that title is created, the link connects automatically — the classic wiki workflow of sketching structure before writing pages.
No. The trigger is guarded: it never fires inside URLs (https://…), inside code blocks or inline code, or in the middle of a word. Writing \// gives you a literal // when you need one.
Yes — that is the point. Files and their connections are served to your AI tools over MCP, so the AI can follow references between docs the way you do, instead of reading isolated pages.
Linked files your whole team — and every AI tool — can follow. Free for individuals.