Skip to content

SoloMD v3.1.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 28 Apr 00:46
v3.1.0
c6c44b7

Agent endpoint — the v4 thrust starts here

The first half of the v4 direction lands. SoloMD is still the same markdown editor; the new story is that any MCP-aware LLM client (Claude Code, Codex CLI, Cursor) can now drive your vault directly through the bundled solomd-mcp server. Same .md files, two ways in — the editor on top, the LLM endpoint underneath.

"A markdown editor — and the bridge to your LLM."

5 SoloMD-only MCP tools

The bundled solomd-mcp grew from 8 to 13 tools. The 5 new ones expose state that only SoloMD knows about — no other markdown MCP server has these.

  • autogit_log — per-note commit history from the local AutoGit repo. Newest first, only commits that touched the path.
  • autogit_diff — unified diff between two AutoGit commits for one note. Smart default: picks the most recent commit that touched the path (vanilla HEAD-vs-parent is empty when HEAD changed other files).
  • autogit_rollback — restore a note's content from a specific SHA. Gated behind --allow-write.
  • sync_status — read SoloMD's GitHub-sync configuration (linked remote, branch, encryption flag, last push/pull). Reads .solomd/sync.json; fails closed on parse error (same security posture as the desktop app's v3.0.x audit fix).
  • share_url — compute the public solomd.app/share/?repo=...&path=...&branch=... URL for a note. Handles branch names with / correctly.

Plus all 8 existing tools (list_notes, read_note, search, get_backlinks, list_tags, get_outline, write_note, append_to_note).

solomd agent CLI launcher

Two new subcommands in scripts/solomd:

  • solomd mcp-config — print a ready-to-paste MCP config snippet pointing at the bundled solomd-mcp and your SOLOMD_NOTES vault.
  • solomd agent <prompt> — generate a one-shot MCP config in TMPDIR, then hand off to whichever LLM CLI is on PATH:
    • Claude Code → claude --mcp-config <cfg> -- <prompt>
    • Codex CLI → prints the ~/.codex/config.toml snippet, then codex <prompt>
    • aider → no MCP support; prints recipe
    • none → friendly install hint

This is deliberately a launcher, not a reimplemented agent loop. You already have the LLM CLI configured with your BYOK keys; SoloMD's job is to put solomd-mcp in front of it.

Other changes

  • README rewritten for the new positioning.
  • 9 new cargo tests in mcp-server/src/tools.rs covering every SoloMD-only inner helper, including regression pins for sync_status_corrupted_json_fails_closed and share_url_handles_branch_with_slash.
  • Windows build: mcp-server/build.rs adds advapi32 / bcrypt / crypt32 / userenv to the link line so libgit2's vendored CryptoAPI calls resolve cleanly without dragging OpenSSL into the sidecar.

Self-test before release

  • 13 MCP tools driven via stdio JSON-RPC end-to-end (initialize → tools/list → 5 SoloMD-only tools)
  • CLI: solomd mcp-config + solomd agent (with all three CLI fallback paths)
  • cargo test: 9 new tests, 0 failures (plus the v3.0.x suite still green)
  • .app boot smoke test on the locally-built dmg before upload
  • CI: Linux x64 + Linux arm64 + Windows + web-clipper — all 4 jobs success, including the first-time-passing install-mcp.sh self-test

Downloads

Same matrix as v3.0.2 — Mac universal dmg (notarized), Windows setup.exe + msi + portable.zip, Linux deb/AppImage/rpm × x64+arm64, plus standalone solomd-mcp archives for each platform and the browser clipper extensions.

Use it

# Tell your AI client about your vault:
solomd mcp-config

# Or run an agent end-to-end:
solomd agent "rewrite this week of dailies into a weekly review and commit it"
Assets 19
Loading