Notula - WYSIWYG Markdown editor for docs as code
Download
ProductHow it worksSafetyStatusFeedback
Early, but running<br>WYSIWYG Markdown editor.For the docs in your git repo.<br>Docs as code , without having to be a coder. Like<br>Google Docs , on files that never leave the repository :<br>comment on a passage, reply, resolve, browse the docs in a tree, and<br>publish without anybody being shown a rebase.
Download for macOS
Download for Windows
See what it does
Free, and it stays free. No account, no server. macOS and Windows.
Your documentation already moved.<br>Your tools did not. What docs as code costs a team.
01 AI writes Markdown<br>Agents read, write and review plain .md natively. Files in the repo are where they are strongest, and where your engineers already review changes.
02 So the docs followed<br>Specs, PRDs, RFCs and runbooks left the wiki and landed next to the code. That was the right call, and nobody is moving them back.
03 And everyone else lost their tools<br>No comments, no threads, no way to browse, no way to edit a paragraph without learning a code editor, a diff and a rebase first.
Everything you use in Google Docs,<br>on files that never leave your repository.
Google Docs Markdown in a code editor Notula<br>Comment on a passage, reply, resolve<br>Told the moment somebody comments or names you<br>See who has changed a document since you opened it<br>Write without seeing any syntax<br>Browse documents in a tree, not a file list<br>Back and forward between linked docs<br>Usable by someone who has never opened a terminal<br>Files stay plain .md in your own repository<br>AI agents can read and edit the same files<br>Reviews as a normal pull request<br>Works with no network and no vendor account<br>Tells your AI agent how the workspace is organised
Speaks git and nothing else, so it works with what you have<br>GitHubGitLabBitbucketGiteaSSH keysGit LFSSubmodulesNo remote at all
Only the documentation, none of the code
Open a repository with thousands of source files and get a clean tree of<br>Markdown. Folders with no documents in them never appear.
How the workspace is built
WYSIWYG, not live preview
No Markdown syntax, ever. No hashes, no asterisks, no table pipes, not<br>even on the line your cursor is on. The file on disk stays ordinary<br>Markdown.
See what it writes back
Mermaid diagrams draw themselves
A mermaid block is a picture in the document, not a wall of arrows and<br>brackets. On disk it is still the same fenced block, so it draws on the<br>host too.
The comments you actually miss<br>Select a passage, leave a comment, reply, resolve.
And they are told, by name
Git, without teaching git
Every version of the document is there to read and to bring back. Nobody<br>is ever shown a rebase, a stash, or the words detached HEAD.
What it will never do
You are never the last to know<br>and nothing ever changes under your cursor.
Somebody named you
Your machine tells you, with the sentence they wrote.
Maya Chen named you<br>Is the order the real problem, or the number of fields?<br>checkout-redesign.md · platform-docs
Clicking it opens the document at that paragraph, not at the top.<br>It keeps watching repositories you do not have open, with the window closed.<br>Two at a time arrive on their own; more than that arrive together, so they stay read.
Something changed
And you did not have to go and ask.
Every document the rest of the team has moved on is marked in the tree, with who moved it and when.<br>Your own unpublished work is marked the same way, so nothing waits in a drawer you forgot about.<br>It looks every thirty seconds while you are working, and every few minutes while you are not.<br>All of it is read from the fetched branch, so the document on screen is still exactly what you left until you take the change.
Threads that live in the repository
A conversation is committed next to the document it is about, so it arrives<br>with the clone and outlives every account.
Documents stay clean. No invisible anchors, no block IDs, no HTML comments.<br>Anchored by the quoted passage and its context, following the W3C Web Annotation model.<br>An append-only log with a union merge driver, so two people commenting at once cannot conflict.
Navigates like a browser
Follow a link and the document opens in the same pane. Back and forward<br>return you to exactly where you were, scroll position included.
Every pane keeps its own trail, so a reference held open in a split is never disturbed.<br>Relative links between documents resolve the way they do on the host.<br>Non-Markdown link targets open read-only instead of being handed to another app.
A one-character edit stays a one-character diff
Notula writes back only what changed. Across 6,000 real documents, 96.4%<br>of blocks survive an edit untouched.
Where the project actually is
Your agent gets a briefing, not a guess<br>Notula writes down how the workspace works, and points Claude Code at it.
It writes notula-agents.md describing the document<br>types, the fields, the layout and the commands, and borrows three<br>lines of your...