detongz/dsh-client-ui-obsidian-memory
Five filesystem tools let the agent read, search, append to and write a local Obsidian or plain Markdown vault, with a status sidebar panel.
This is persistent memory with no server and no database: the agent's memory is a folder of Markdown files you can open in Obsidian and edit by hand. It registers five tools — obsidian_memory_read, obsidian_memory_list, obsidian_memory_search (full text across .md and .txt), obsidian_memory_write and obsidian_memory_append — and mounts a sidebar panel that browses the vault and lists the tool reference. Because the tools go through DSH's host runtime straight to the filesystem, everything the agent remembers is inspectable, diffable and reversible with normal file tools, which is the opposite trade from an embedding store: recall is exact string search over notes you can read. The author credits the Codex memory technique as the inspiration.
Install
dsh plugin add dsh-client-ui-obsidian-memoryThe plugin ships a dsh.bundle manifest, so dsh plugin add installs the package and activates it as a profile layer — the bundled cordis.patch.yml inserts the obsidian-memory entry, so no manual patch edit is needed to load it. The one required setting is vaultPath in your profile's cordis.patch.yml, which must be an absolute path to the Codex folder you create. Lifecycle scripts are declared explicitly (a prepare step running npm run build).
Compatibility
No network access at all — the README states the plugin makes no outbound requests. Reads and writes are confined to the directory given by vaultPath; no commands and no credentials required. It follows the community Codex/ directory convention (AGENTS.md, TODO.md, people/, projects/, notes/, daily/), so a vault already shaped that way works without restructuring.
Details
- Repo: detongz/dsh-client-ui-obsidian-memory
- Category: Memory
- Stars: 15
- Version: 0.3.2 (npm)
Alternatives
bonerush/dsh-obsidian-mem · dearbld/dsh-living-memory · ICCuse/dsh-file-memory