Memory that behaves like part of the codebase.
Travels with the code
Memory lives inside the repo it describes. Move the folder, branch it, share it — the context comes with it.
Layered context
Org, project, user, and local memory merge into every prompt. Personal notes never leak into the team's shared knowledge.
Human-in-the-loop
Agents propose; you approve. Nothing committed gets silently rewritten. Routine session logs auto-save in the background.
Built for swarms
Worktree-safe and orchestrator-mediated, so concurrent agents can read shared context without trampling each other's work.
One context, four sources.
Each tier covers a different scope. They merge in order — broader context first, more specific context last — so personal preferences can refine team standards without overwriting them.
Agents draft. You decide.
Auto-saving everything an agent says is how memory gets noisy fast. We split it: chat sessions log themselves, but anything that touches committed knowledge goes through a review queue.
Agent proposes
When an agent learns something worth keeping — a decision, a pattern, a gotcha — it drafts a memory entry instead of editing files directly.
You review
Proposals land in a queue with full context. Accept as-is, edit and accept, or dismiss — your call.
Memory commits
Approved entries land in the right tier, tagged and indexed. Next agent that opens the workspace inherits the new context automatically.
- Memory moves with the folder — no central registry.
- Loaded straight into context — no vector database to manage.
- Personal layer is gitignored — your notes stay yours.
- Concurrent agents are isolated by worktree, never racing on memory.
Memory that travels with your repo.
DevMemory lives inside the DevMesh desktop app — tiered context, human-in-the-loop proposals, no vector DB to babysit. Open the app and your agents stop forgetting.