claude mcp add --scope user markdown-notes-agent -- markdown-notes-agent serve

codex mcp add markdown-notes-agent -- markdown-notes-agent serve

Update the source installation with these commands.

uv tool install --force git+https://github.com/woonyong-choi/markdown-notes-agent
markdown-notes-agent setup

The Hanger 0.2.0 tag from before the rename is preserved. When moving an existing installation, stop the existing service and move state, search data, request keys and recovery files to the new paths without losing their contents. Preserve folder rules and ignore rules under the new file names, and update explicit relation identifiers and MCP connections before starting. This version does not automatically connect old command or module names.

Install from source with this command.

uv tool install git+https://github.com/woonyong-choi/markdown-notes-agent

VAULT.md can sit in any folder and applies to that folder and below. For settings between the top --- lines, the nearest file wins. For each note path, Markdown Notes Agent selects written rules from the nearest folder first, up to a total of 32 KiB, then sends the selected rules from the root down to the nearest folder. The file has its own name so it does not mix with other AI tools' rule files (AGENTS.md, CLAUDE.md and so on).

---
write: false
---

Notes in this folder are final. Quote them; do not change them.

One note is one concept. Broader concepts the user wrote come first: a parent in the front matter (a slug, file name or link), and index notes whose list lines start with a link (that note is the parent of the notes it lists). Where the user wrote nothing, the model reads the note with its 20 nearest notes and proposes a concept name, other names, a definition and broader, related and prerequisite concepts; the program checks and stores them.

• A broader concept must be in the same tree and cannot form a cycle.
• A new broader name joins a note or concept of the same name; otherwise it becomes a concept when a second note proposes it, and goes back to waiting if it drops to one child.
• A concept with more than 15 direct children is split into narrower groups by the model.
• When a note is deleted, its children move up a level and are placed again.
• Notes that answer the same central question are reported, and when both folders set merge: auto a merge job is queued. Merges are reviewed like any other change.
• Concept names and other names add lightly to search, so a note is found by names its text never uses. Search results and drafts carry a note's place when the note belongs to the tree.

The tree is built in the background, one note at a time, while no user request waits. markdown-notes-agent keywords and list_vaults show progress.

Editing the patterns in .markdown-notes-agentignore or deleting the file does not take effect at once; it is recorded as a decision. An edit that only changes comments cannot affect the index and applies at once. While a decision is pending, Markdown Notes Agent refuses every search and change request and asks for the answer first. If a vault's folder is missing or empty (an unplugged drive, say), its decision is withdrawn and asked again when the folder is back. File watching and index updates keep running. Markdown Notes Agent asks because a note taken out of the index may not get the same keywords and links when it is indexed again. For a deleted file, approving recreates the default file and declining restores the previous one.

Connected as an MCP server, Markdown Notes Agent offers these tools. Its messages and questions are in English, and it tells AI tools to translate them into the user's language.

With more than one vault, each request passes vault as an id or a path inside the vault. Usage guidance for AI tools is in skills/markdown-notes-agent/SKILL.md.

Main settings:

Settings, the vault list, applied ignore rules and decisions are stored in ~/.local/share/markdown-notes-agent/state/markdown-notes-agent.db. Setting changes apply when the service restarts (markdown-notes-agent stop).

change-request.diagramplay is the source; the SVG is generated. Set DIAGRAMPLAY_CLI to the CLI path from DiagramPlay ebdc3e9.

node "$DIAGRAMPLAY_CLI" check docs/assets/change-request.diagramplay --strict
node "$DIAGRAMPLAY_CLI" render docs/assets/change-request.diagramplay --strict --out docs/assets