SoloMD CLI
solomd is a small binary that exercises the same domain
functions as the GUI — open a note, create one, search the vault, list
files, print to stdout. Built for shell pipelines, cron jobs, and
muscle-memory ops.
Install
macOS / Linux — paste this in your terminal:
curl -fsSL https://raw.githubusercontent.com/zhitongblog/solomd/main/scripts/install-cli.sh | bash
It drops a solomd binary into /usr/local/bin.
Windows users can grab the standalone solomd.exe from
the releases page
and add it to %PATH%.
Subcommands
| Command | What it does |
|---|---|
solomd open <title|path> | Open a note in SoloMD. Title-as-arg uses fuzzy match against the vault. |
solomd new <title> [text] | Create a new note with the given title and optional body, then open it. |
solomd list [folder] | List Markdown files in the workspace (or a sub-folder). |
solomd search <query> | Grep your notes. Returns paths + matching lines. |
solomd cat <title|path> | Print a note to stdout — pipe into pandoc, fzf, anything. |
solomd help | Show the full subcommand list. |
Examples
# Quick capture from anywhere
solomd new "standup 2026-04-26" "$(pbpaste)"
# Find every note that mentions "rust"
solomd search rust
# Pipe a note through pandoc
solomd cat "weekly-review" | pandoc -t docx -o weekly-review.docx
# Cron: append a daily journal stub each morning
solomd new "$(date +%F)" "## $(date +%A)
- [ ] "How it finds your vault
The CLI reads the same solomd-language /
solomd-workspace preference files the GUI writes. If
you've opened a folder in SoloMD recently, the CLI will use that as
its workspace. To override, set SOLOMD_WORKSPACE:
SOLOMD_WORKSPACE=/path/to/notes solomd listCombined with the MCP server
The CLI is what the user types; solomd-mcp is what the AI
calls. They share the same workspace state, so a model can write a new
note via MCP and you can immediately solomd open it from
the terminal — no reload, no race.
See MCP server for the AI side.