dsh-markdown-memory

Most agent memory schemes write facts into a vector store or a hosted service, locking your memory behind one engine or one platform. Switch to a different agent and you wire it back up; want to edit a single line and you route through an external API. dsh-markdown-memory takes the simplest possible route: your memory is a Markdown folder you already own. Each durable fact lives in its own file with YAML frontmatter, and a single index file lists every entry. The plugin injects that index together with a recursive file listing into the system prompt; the model opens individual files on demand with its file tools, incurring no token cost until it actually reads one.

On top of that minimal structure the plugin offers two active delivery mechanisms. Memories marked as seed are injected automatically at session start, suited to background facts the model should hold before any question arrives. Unmarked memories are recalled on demand via trigger strings declared in their frontmatter, performing literal substring matching against the text entering each step and appending only when relevant. Both paths share deduplication, byte budgets, and truncation guards so nothing is silently dropped.

If you already manage notes in Obsidian, that vault is your memory folder and mounts directly. If you just want memory you can git diff, share across agents, and delete a line of by hand, without standing up an embedding pipeline or depending on a cloud service, dsh-markdown-memory is the option where pointing at a folder is the whole setup.