A WYSIWYG surface and the raw Markdown, both writing to the same file.
Mindex has two ways of looking at the same note, and they are the same note.
Both write back to the one file. There is no import step between them and no canonical "real" version hiding behind the other: the file is the document, and rich mode is a way of editing it.
This matters more than it sounds. Most WYSIWYG note apps store something else — a document model, a database row — and produce Markdown on export. What you export is then a rendering of the truth rather than the truth. Here the Markdown is what you edited.
Write the way you would in any editor. Formatting applies as you go, wiki links
autocomplete from [[, and pasted links and Markdown are detected and
converted. ⌘⇧V / Ctrl+Shift+V pastes the clipboard as
plain text when you would rather it did not.
Use it when you need the file itself: fixing frontmatter by hand, repairing unusual Markdown, or making an exact textual change.
⌘F / Ctrl+F searches the open note. Enter and Shift+Enter move between matches.
⌘⇧+ and ⌘⇧- change the size of the note's text only. ⌘+ and ⌘- zoom the whole window. ⌘⇧0 and ⌘0 reset them.
Select any passage and ask for a rewrite. While the assistant works, the passage is lit in that assistant's own colour, where it sits in the note. The answer arrives in place — your wording struck through, the wording on offer underlined after it — and under the block, two answers: accept it or decline it. Nothing is written to the file until you accept. See Rewrite a passage with AI.
Select a passage and press Comment to open a thread beside the note. A comment is anchored to the words rather than to a position, so it survives the note being rewritten around it. See Comments.
Saving is automatic, and each write is snapshotted locally: the clock in the tab row opens the note's timeline, the difference against the file as it stands now, and a way back. See History.