

MemoryCustodian gives Codex, Claude Code, Gemini, and other coding agents durable project memory—without a hosted service or bloating every prompt. Decisions, constraints, rejected approaches, and project context live as plain Markdown in your repo, where they can be reviewed, versioned, shared, and deleted like code. A manifest loads only the memory relevant to each task. Open source, local-first, and cross-agent.
Loading comments…
Project Info
Product Keywords
MemoryCustodian is an open-source, local-first tool that gives coding agents—like Codex, Claude Code, and Gemini—durable project memory without requiring a hosted service or bloating every prompt. It stores decisions, constraints, rejected approaches, and project context as plain Markdown files directly in your repository. A manifest system loads only the memory relevant to each task, keeping agent sessions focused and efficient. MemoryCustodian is designed to be reviewed, versioned, shared, and deleted like code, making it a natural fit for any development workflow.
Memory is stored as standard Markdown files in your repository, so humans can review, edit, and version them just like code. No proprietary formats, no external databases—just files that work with your existing Git workflow.
A manifest.md file routes the agent to only the memory files relevant to the current task. Instead of loading everything, the agent reads brief.md for project shape, decisions.md and constraints.md for planning, and do-not-use.md to avoid rejected paths—keeping context minimal and focused.
MemoryCustodian works with Codex, Claude Code, Gemini, and other coding agents. A single init command creates bootstrap files for your chosen agent, and the same memory structure works across different tools and platforms.
Optional directories like rules/, profiles/, areas/, and archive/ stay out of the default context until they are explicitly relevant. This prevents memory bloat and ensures agents only load what they need for the task at hand.
"Durable memory. Minimal context."
This one-liner captures MemoryCustodian's core philosophy: it gives agents lasting project knowledge without inflating every prompt. By storing memory as plain Markdown in the repo and loading only what's needed per task, it avoids the common trade-off between memory depth and prompt efficiency. The result is a system that feels invisible—agents remember what matters, and you never pay for context you don't use.
You're tired of repeating the same project context to your coding agents every session, or you want a lightweight, open-source alternative to hosted memory services. MemoryCustodian is especially useful if you value local-first tools, version-controlled project knowledge, and the ability to review and curate what your agents remember. It's a practical fit for any team or solo developer using AI coding assistants who wants durable, minimal, and shareable project memory.
Other tools you might consider
GitHits gives coding agents access to the open-source code your app depends on. Get real implementation examples, dependency source navigation, package inspection and documentation. Agents can grep and read your codebase. They can't grep and read the open-source code your app depends on. That's where they start guessing, retrying, and looping. GitHits builds a version-aware index on demand. Agents can search, navigate, and inspect the code behind their dependencies. CLI: npx githits@latest init
You're running more coding agents than ever, but you can't keep up with them. That's where AgentPeek comes in. It pulls every session up into your Mac notch, live. Glance up, approve a prompt, watch token usage and manage the entire flow without pausing your YouTube video. All local, all yours.
Most agents pass their evals and fail in production. Prefactor is the evaluation layer that closes the gap. We score every agent run in real time, surface quality regressions and drift as they happen, and show engineering teams exactly how their agents are performing at scale. Built for the teams shipping agents to customers.
The moment an agent needs to deploy something, it slams face-first into a wall built for humans. Today we're rolling out Temporary Accounts on Cloudflare Workers. Any agent can now run wrangler deploy — temporary and get a live Worker in seconds.
Maker
neon_dev
Alternatives
Loading comments…