- better note organization with types and relationships - different, more Notion-like UX - first class support for git as sync + version control layer - long tail of design decisions that help AI work well with vaults: types, MCP, git authorship, etc - and most of all... open source!
Worth watching how each of these tools positions the AI: as a UX copilot inside the editor, or as an autonomous agent with file-system access via local CLI/MCP.
I've been working on this split in a side project (https://github.com/rillmd/rill — vault layer on top of Claude Code). Git still handles the durable side for free, since the CLI agent just writes files and commits normally. The live side comes from Claude Code hooks (UserPromptSubmit / Stop / PostToolUse) appending to a plain activity-log.md that the Electron GUI tails. Cruder than Google Docs cursor presence, but cheap — and the log itself is just another markdown file in the vault, same data model as everything else.
One trade-off: going the other direction and letting the frontend detect edits via FSEvents-style watching runs straight into the reconciliation issues the Zettlr subthread is about. Hooks on the agent side are less elegant but sidestep the whole class.
Typora? (https://typora.io/)
HelixNotes? ( https://codeberg.org/ArkHost/HelixNotes )
It's so good for viewing all markdown in a repo, but dies all too often.