Project-local memory.
+Each repo keeps its own working state. You can link broader context when you want it, not before.
+
+
+
+
+
+
+
+ GitHub Pages demo
+
+ Keep context when sessions end.
++ Muse Memory is a local-first memory layer for agents. It keeps project facts, working constraints, and handoffs in one place, so the next session starts with the same picture. +
+ + +
+
+
+ 
+
+
+
+
+
+
+
+
+
+
+ Up and running in minutes
+
+ Install it locally, then point it at the workspace.
++ Start with one command, keep the current task in view, and use the same store from the CLI, the MCP server, or the dashboard. +
+
+
+
+
+
+
+ Quick start
+
+
+
+
+
+
+
+
+
+
+ bunx musememory install
+ Best when Bun is already installed.
+
+
+
+
+
+
+
+
+
+
+ What it keeps in view
+
+ The system is useful when it stays out of the way.
++ These are the parts that matter most when the work spans multiple sessions, multiple tools, and more than one agent. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Current work stays visible.
+The active task, open loops, and handoff notes live in plain Markdown so a new session can pick them up fast.
+Why and provenance travel with the memory.
+Claims keep their source trail, so the next person or agent can see what changed and why it was kept.
+Secret defense is built in.
+Vibeguard checks for obvious credentials before they land in memory, so the store does not become a leak path.
+
+
+
+
+
+
+
+ Built in the open
+
+ It sits beside the editor, the terminal, and the agent loop.
++ The page stays close to the same rhythm as the reference site: a simple promise up top, one practical way to begin, and a section that shows where it fits in the real workflow. +
+
+
+
+ Works with the tools you already use.
+
+ Muse Memory plugs into CLI agents, MCP clients, and the local dashboard without asking for a new workflow.
+
+ Claude Code
+ Cursor
+ Codex
+ OpenCode
+ Windsurf
+ Gemini CLI
+ MCP clients
+ Obsidian
+ GitHub
+
+
+ 
+
+
+
+
+
+
+
+
+
+ Always improving
+
+ The store gets trimmed, the handoff stays current, and the studio keeps the state visible.
++ This section mirrors the reference layout's release area, but keeps the copy grounded in what Muse Memory actually does today. +
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Less noise, less drift.
+Use the optimizer when the store needs a clean pass. It trims low-value clutter and keeps the useful parts near the surface.
+One place to see the current state.
+The dashboard keeps health, workstreams, and active constraints visible without asking you to dig through separate files.
+Parallel sessions without guesswork.
+Multiple agents can stay coordinated because the active task and next step are written down where everyone can see them.
+
+
+
+
+
+
+ Ready when you are
+
+ Keep the memory close.
++ If the work matters tomorrow, it belongs in Muse Memory today. Start local, keep the state visible, and let the next session begin with context instead of guesswork. +
+ +