Repo-native Markdown memory
Stores decisions, constraints, rejected ideas, and project context in plain Markdown files that live in the repository, so humans can review and version them like code.
MemoryCustodian
MemoryCustodian is a repo-native memory system for coding agents. It stores decisions, constraints, and rejected ideas in plain Markdown so agents can load just the context needed for the current task.
Project memory for coding agents
MemoryCustodian is a repository-based memory system for coding agents. It helps teams preserve decisions, constraints, rejected approaches, and current project context in plain Markdown so future sessions can load only the information that matters for the task at hand.
The product is designed to reduce the need for re-pasting project history into prompts or platform instruction files. Instead of keeping memory inside chat logs, it keeps durable context inside the repo, where humans can review and update it alongside code.
Core capabilities
Selective context loading
Loads only the files needed for the current task, starting from `manifest.md` and `brief.md` and then pulling in task-relevant memory files instead of the whole project history.
Minimal agent bootstraps
Uses a thin bootstrap layer for `AGENTS.md`, `CLAUDE.md`, `GEMINI.md`, and similar files, so platform-specific instructions point agents to durable memory without duplicating it.
Structured memory layout
Creates a default memory structure with `manifest.md`, `brief.md`, `decisions.md`, `constraints.md`, `do-not-use.md`, and `inbox.md`, with optional `rules/`, `profiles/`, `areas/`, and `archive/` folders.
Guarded maintenance workflows
Includes CLI flows for initialization, repair, preview-first replacement, and managed bootstrap block updates, giving teams bounded ways to create and maintain memory files.
Multi-agent setup paths
Provides support for local plugin and source-checkout setups, including Codex, Claude Code, and Gemini agent paths, so the same repository memory can be reused across agent environments.
Common workflows
Starting a fresh coding session
A new agent session can recover architecture constraints, preferred workflows, and rejected ideas before proposing changes, which reduces relearning at the start of each task.
Maintaining shared project memory
Teams can keep durable project context in repo files instead of chat transcripts, making decisions easier to review, update, and discuss in code review.
Using the same memory across agents
When working across different agent setups, the same repository memory can be loaded through thin platform bootstraps and agent-specific install paths rather than duplicated manually.
Bootstrapping or repairing an existing repo
A project can initialize or repair its memory files with the CLI, including preview-first replacement and managed bootstrap block updates, while keeping curated memory intact.
Recovering prior implementation constraints
The NightNotes evaluation demonstrates how an agent can use the repository memory to recover a JSON storage decision, offline-only operation, and a standard-library constraint before planning implementation.
Pros and Cons
Pros
- Keeps project memory in plain Markdown inside the repository, which makes the content diffable and easy to inspect.
- Loads only the context relevant to the current task, which helps avoid sending unnecessary project history into the working context.
- Supports a repeatable initialization and repair workflow through the CLI, including preview-first replacement behavior for existing setups.
- Separates durable memory from thin agent bootstraps, which keeps platform files small while preserving project-specific knowledge.
- Offers documented evidence of a reproducible live evaluation where an agent recovered prior decisions, constraints, and a rejected SQLite approach from memory.
Cons
- The public source shows the main workflow clearly, but it gives only partial detail on integrations and external agent support beyond the mentioned Codex, Claude Code, and Gemini paths.
- The README emphasizes careful initialization and curation, so it is not a drop-in memory store without some project setup and review.
FAQ
What is MemoryCustodian for?
It is a repo-native memory system for coding agents. It stores project memory in plain Markdown files inside the repository and loads only the context relevant to the current task.
How is it set up in a project?
The README says to initialize it once per target project with the CLI, using a command such as `memory-custodian init --project-root /path/to/project --agent all`. The initial setup creates a `brief.md` scaffold and the core memory files under `docs/memory/`.
Which agent workflows does it support?
The documentation describes local plugin and source-checkout workflows, with support for Codex, Claude Code, and Gemini agent setup paths. The core workflow is repository-based rather than tied to a single hosted service.
Does it require Codex or GPT-5.6 at runtime?
The product is designed around thin platform bootstrap files and durable memory in the repo. It is not presented as runtime-dependent infrastructure, and the README emphasizes that Codex and GPT-5.6 were used to build and validate it, not as runtime dependencies.
Can it update existing memory without overwriting curated content?
The README says that a full replacement flow is preview-first and that repair mode updates known generated metadata without overwriting curated memory. It also notes that optional areas such as rules, profiles, and areas stay out of the default context unless the manifest explicitly includes them.
Quick Facts
- Category
- Developer Tool
- Product type
- Repo-native project memory system
- Primary users
- Coding agents and developers working with agent-assisted repositories
- Source domain
- github.com
- Pricing
- Free and paid GitHub plans are available; the repository itself is public on GitHub
- Supported setup paths
- Codex, Claude Code, Gemini, and source-checkout workflows
Alternatives à MemoryCustodian
ByteAsk
ByteAsk is a terminal-first AI coding agent for C and C++ that edits repositories and verifies changes with the real compiler, debugger, sanitizers, and tests before showing a diff. It offers a free tier plus paid plans, with editor connectors and zero-retention handling described in the source.
CreateOS Sandbox
CreateOS Sandbox is an isolated compute environment for running code and agent workloads inside Firecracker micro-VMs. It is designed for workflows that need machine-level isolation, private networking between sandboxes, and programmatic control through SDK, CLI, or MCP.
hob
hob is an independent workspace for coding agents that keeps agent sessions, terminals, history, and follow-up work organized around the tools and providers you already use. It is aimed at developers who want local control over routing, history, and workspace structure rather than a bundled model stack.
Manta AI
Manta AI is an autonomous web app testing tool for teams that want to map application behavior, catch regressions, and generate tests without writing scripts or maintaining selectors. It works from a URL and supports plain-English test flows, run results with screenshots, and scheduled or deployment-triggered checks.
SonOf
SonOf connects to your repo and PM tool, audits the codebase and surrounding product context, and turns approved work into shipped tickets with senior engineering review. It is aimed at founders and engineering leaders who need backlog help without hiring a full team immediately.
Ghost
Ghost est un assistant IA en terminal pour discuter, générer du code et lancer des tâches en ligne de commande. Modèles gratuits, Linux, macOS, Windows, open source.