zhitongblog/solomd: README-based editorial guide
A guide grounded in the README, repository metadata, and license for installing and checking zhitongblog/solomd.
Project scope
zhitongblog/solomd describes itself in the README as "A markdown editor , and the bridge to your LLM. Local-first, MIT, 15 MB. Bundled MCP server lets Claude Code / Codex / Cursor drive your vault directly. 14 AI providers BYOK.". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "SoloMD", the README says: Your notes live in a folder. SoloMD is the editor on top , with a first-class agent surface inside the editor, and the MCP endpoint Claude Code / Cursor can drive from outside. Same .md files. Chat with your vault.. That establishes the project's stated boundary, not a production test.
Suitable use cases
The README's "New in 4.6 , the knowledge-graph layer" section gives a useful starting point for deciding whether the project fits: Type-driven sidebar , give a note type: Project and its members become a first-class collapsible section with custom icon/colour/columns (types-as-lenses).. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: Properties inspector (⌘⇧I) , edit YAML frontmatter with type/date/status/relation pickers; line-surgical writes preserve your comments, inline arrays and quoting byte-for-byte.. It can shape a first test, but it does not replace testing in the intended environment.
How it works
The operating model is spread across sections such as "New in 4.6 , the knowledge-graph layer". The source evidence includes: The structural half Obsidian and Tolaria had and SoloMD didn't , now built, and on SoloMD's own warm design system:. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.
Installation and first run
Start installation from the README's documented entry point. A command that can be checked in the source is: brew install --cask zhitongblog/solomd/solomd When the README contains no runnable command, this article does not invent one. Open its "New in 4.6 , the knowledge-graph layer" section and confirm system dependencies, default ports, and first-run initialization before using a public server.