What the editor does

No fiddly setup. Rich writing tools that live right on top of markdown.

[[wikilink]] autocomplete

Start typing and candidate notes and concepts surface. Links resolve to real files first. If the target doesn't exist yet, nothing breaks — the link quietly stays as is.

Slash menu & in-document search

One slash inserts blocks, math, diagrams, and tables. Search instantly even inside long notes and jump to the line you want.

Math · diagrams

Inline or block, math renders as written. Diagrams like flowcharts, sequences, and graphs render too. All of it works inside plain markdown code blocks.

Tables · footnotes · image/video · PDF preview

Tables and footnotes, images and video, even previews of attached PDFs. Keep your material in one document instead of scattering it.

Multi-document tabs · multi-window · PDF export

Open several notes as tabs. Split into windows to see them side by side when you need to. Export a finished document straight to PDF.

File tree · drag and drop · live external changes

Organize with the familiar right-click menu and drag and drop. Change a file elsewhere and it's reflected in real time.

Notes are the source; the graph is something you can rebuild

Markdown is a language both people and AI speak fluently. It's also the easiest way to edit a graph.

01

You edit the graph in markdown

Your notes are plain markdown files sitting right on your device. Use tables, math, diagrams, and wikilinks freely in the editor. Markdown is the easiest path to editing the graph.

02

The system never touches your writing

Notes are unchanging memory — the source of truth. The concepts and relationships it derives, plus search and the graph, are all rebuilt alongside them. Your sentences themselves are never altered.

03

Save, and the graph grows

Every save derives concepts and relationships from the markdown and weaves them into a knowledge graph. Agents reason along this web of connections to answer. The graph can always be rebuilt from your writing.

Write first, and grow the graph underneath

Local-first. Write plain markdown and a knowledge graph grows beneath it. Agents reason on top of it to do the work.

Download →See the ontology graph →

Personal knowledge

You don't need the right search term

A product manager with five years and 1,800 notes finds his own writing using a concept that appears nowhere in the title. Not a real customer story — a hypothetical scenario we thought through.

Across 1,800 notes, asking "what did I write up about the subscription economy last year?" surfaces notes that never use the phrase in the title or the body as "Related", and the "Where this came from in your notes" card separates the direct hits from the ones reached by walking relations.

Example · Hypothetical scenarioRead case →Grad school · Immunology

Why did I switch protocols again?

A fourth-year immunology PhD student, four months out from her defense, gets her own two-year-old decision back verbatim. Not a real customer story — a hypothetical scenario we thought through.

In a workspace holding 900 literature notes and 400 experiment records, asking "every judgment I wrote about Protocol B, in order" returns the sentence written two years ago word for word, along with which note it came from and which line.

Example · Hypothetical scenarioRead case →Solo design studio

"We never said that"

A brand designer covering nine clients alone keeps what each client said in a meeting word for word, with the speaker attached. This is a hypothetical scenario, not a real customer story.

Across 12 meeting notes and 60-odd feedback emails, asking "what did Client A say about type direction?" returns the founder's own sentence, with her name on it and a "ClientA-0312-meeting · line 14" citation.

Example · Hypothetical scenarioRead case →

The easiest way to edit a graph.