Hem Vault
Memory that outlasts the chat
Obsidian vault + MCP so coding agents keep decisions, process, and today’s work.
What it is
A portable second brain for agents
You browse and edit markdown in Obsidian. Agents read and write through MCP under a shared memory policy. Process lives in the vault — soft prefs, binding rules, and playbooks — so you extend the product without shipping new server code.
Features
Built for lasting context
Vault & memory
Search, read, and remember across an Obsidian vault. Project packs keyed to git repos.
Learn moreGuidance
Instructions, soft suggestions, and workflows — extend process without changing server code.
Learn moreOrchesto
Multi-phase delivery with vault personas: plan, validations, review, bounded fix loops.
Learn more
How it fits
Vault, MCP, harness
Three layers: your Obsidian vault as source of truth, the Hem Vault MCP server as structured I/O, and a short memory policy injected into Cursor, Claude, Codex, or Zed.
How it worksDocumentation
Features, guides, and the full MCP reference
Everything in the product docs — how to use each surface, and how it works under the hood.