Brain.Md
A file-based persistent memory layer for coding agents—no runtime, just Markdown.
An elegantly minimal solution to a real pain point—if you're disciplined enough to compile decisions, it's a must-try for Claude Code or Codex users. No other tool achieves persistent memory with such low overhead and zero dependencies. Compared to cloud memory services, it gives full data ownership and Git-native provenance, but it requires a workflow change: you must consciously trigger 'brain update-truth' rather than have memory captured automatically. If you want automated retrieval and semantic search, look at Mem0 or Cursor's memory features, which are heavier but more hands-off.
Verified 4d ago · liveness 45/100 · cite: rightaichoice.com/tools/brain-md
- Developers using Claude Code or Codex for long-running projects
- Teams seeking to preserve AI context across sessions without cloud services
- Solo developers who want to avoid re-explaining context in new chats
- Open-source maintainers documenting architectural decisions for AI contributors
- Users who prefer GUI-based knowledge management tools
- Teams reliant on cloud-hosted memory services with built-in retrieval and semantic search
- Projects where coding agents cannot read Markdown files (e.g., web-only chat interfaces)
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip BRAIN.md if you expect AI memory to be captured automatically without manual effort—it requires you to consciously run 'brain update-truth' after decisions, and won't be useful for GUI-based or web-only chat workflows.
Requires Node.js installed on every machine that runs the CLI—a hidden prerequisite if your team's environment doesn't have it
BRAIN.md is free and open source, so it beats paid memory services like Mem0 or Cursor's enterprise tiers on price. For solo developers and small teams who don't mind manual upkeep, it's the cheapest way to get persistent AI memory. If you need zero maintenance, you'll pay in time—or money—for an automated alternative.
In short
Brain.Md — A file-based persistent memory layer for coding agents—no runtime, just Markdown. Best for Developers using Claude Code or Codex for long-running projects, Teams seeking to preserve AI context across sessions without cloud services, Solo developers who want to avoid re-explaining context in new chats. Free to use.
What people actually say about Brain.Md — is it worth it?
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
2 mentions across 1 source (Hacker News) · researched Jul 3, 2026.
- +Zero-dependency CLI works offline, no servers required.
- +File-based Markdown memory is Git-versionable and portable.
- +Free and open source—no subscription or API keys needed.
- +Structured six-page root gives agents a consistent project overview.
- +Granular pages with compiled_truth and timeline capture decision history.
- −Very slim community feedback—only 2 Hacker News posts available.
- −No integrations with common tools like Slack or Zapier.
- −Agent compliance is not guaranteed; agents may ignore the brain.
- −Manual process could become neglected in fast-paced projects.
- −Success depends on team discipline to keep brain updated.
- • No hidden costs—fully free and open source.
Viability Score
How well maintained and how widely used is Brain.Md? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: September 2026
How we score →Key Features
- Zero-dependency CLI written in plain Node.js
- File-based Markdown memory layer with no runtime daemon
- Six fixed root pages: background, architecture, flow, mindmap, stack, roadmap
- Granular pages with five knowledge types: decision, concept, project, person, reference
- compiled_truth and timeline sections on every page
- Atomic write: update-truth rewrites compiled_truth and appends timeline entry together
- Wiki-link cross-references with [[page-id]] syntax and lint-links validation
- Automatic reindexing of brain/ via reindex command
- Git-versionable history: track decisions alongside code
- Works offline with no network or cloud dependency
- Agent-agnostic: works with Claude Code, Codex, and any Markdown-reading agent
- Setup script installs 4 skills globally for Claude Code and Codex
- brain-setup and brain-bootstrap commands for scaffolding
- No npm install required: runs on plain Node.js
- BRAIN.md protocol entry point compatible with any coding agent
About Brain.Md
BRAIN.md solves the problem of AI agents forgetting context between sessions by providing a persistent, file-based memory layer that lives as a Markdown folder inside your repository. Instead of re-explaining decisions and constraints in every new chat, you compile them into structured knowledge that any coding agent can read on startup. The brain is entirely offline-first: no runtime daemon, no MCP server, no cloud dependency—it ships with your repo and can be versioned with Git. Designed for developers using code-generation agents like Claude Code and GitHub Copilot Codex, BRAIN.md uses a zero-dependency CLI (plain Node.js) to atomically update compiled truths and append timeline entries. The project includes six fixed root pages (background, architecture, flow, mindmap, stack, roadmap) for project-wide views, plus granular pages in five categories (decision, concept, project, person, reference) that track authoritative conclusions and evidence chains. The structure enforces correctness: every write goes through the CLI, guaranteeing atomic updates and valid frontmatter. Wiki-link cross-references with [[page-id]] syntax let you link pages, and a lint-links command validates all references. Because everything is Markdown files in a brain/ folder, the entire history is Git-native—you can diff decisions over time. BRAIN.md is free and open source. It competes with cloud-hosted memory services and MCP-based context providers, but its key differentiator is portability: the brain is a folder you commit, clone, and share with any agent that can read Markdown. For teams that want zero infrastructure and full control, this is the simplest way to make AI agents remember.
Behind the Verdict
BRAIN.md is a sharp, opinionated answer to a problem every developer using Claude Code or Codex hits: the agent forgets everything between sessions. The core insight is to treat memory as a folder of Markdown files, not a service. That gives you three big advantages. First, zero lock-in—the brain is just files, so you can move it with your repo, read it with any Markdown tool, and switch agents freely. Second, provenance—every decision is timestamped, every change is in Git, so you can diff and audit why things were built this way. Third, simplicity—no daemon, no MCP server, no cloud bill; you just need Node.js. The atomic write guarantee via the CLI is a nice safety net: you can't accidentally rewrite a truth without leaving a timeline entry, which keeps the evidence chain intact. The setup script that installs skills for Claude Code and Codex lowers the barrier to entry for the two biggest coding agents. The main weakness is the manual discipline it demands. BRAIN.md won't work if you don't remember to run 'brain update-truth' after each meaningful decision. It's not an automatic memory system; it's a structured note-taking tool that's optimized for AI consumption. If you're the kind of developer who writes extensive documentation for your future self, you'll love it. If you want set-and-forget memory, you'll be frustrated. It's also not a replacement for a knowledge base with semantic search; the timeline is append-only and flat, so if you need to query across pages, you'll rely on grep and lint-links. For solo developers and small teams who are already disciplined, this is a great fit. For larger orgs that need centralized memory and access control, a cloud service like Mem0 might be more appropriate, though it costs money and adds a dependency.
Researching Brain.Md? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas Brain.Md actually fits — and what changes day-one when you adopt it.
You hit a persistence architectural decision in an existing session and want to record it so future sessions remember.
Outcome: You run 'brain update-truth --id persistence-strategy', the CLI atomically writes the conclusion and timeline entry, and your next Claude Code session reads the brain and immediately knows your decisions.
You want to ensure every AI contributor (and human) can understand the project's key decisions without reading long history.
Outcome: You commit a brain/ folder with decisions like 'Why Postgres over MySQL', and new agents read BRAIN.md on startup, reducing repetitive questions and keeping contributions on-spec.
You need to onboard a new teammate and their AI assistant to the project's architecture and tech stack choices.
Outcome: You run 'brain-setup' to scaffold the brain, then 'brain reindex' to generate the index, and the new teammate's Codex starts with full context, so they begin productive work immediately.
Use Cases
- Record architectural decisions and their rationale for future AI sessions
- Keep agents up to date with evolving constraints, tech stack choices, and trade-offs
- Onboard new AI agents to a pre-existing project with full context in seconds
- Audit past decisions by reviewing the timeline of each knowledge page
- Share project brain across team members via Git for consistent AI behavior
Limitations
- This tool is a file-based memory layer with no runtime service or MCP server; it uses plain Markdown files and a zero-dependency CLI.
- Writing to the brain requires CLI-driven updates, and collaboration and cloud sync depend on Git.
- The protocol entry point is a single BRAIN.md at the project root.
as of 2026-08-23
Verification history
We have re-verified Brain.Md 6 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-checked, vendor evidence unchanged
- — re-checked, vendor evidence unchanged
- — re-checked, vendor evidence unchanged
- — re-checked, vendor evidence unchanged
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
Free to cite with attribution — this page re-verifies continuously.
Where the pricing makes sense
The company stage and team size where Brain.Md's pricing actually pencils out — and where peers do it cheaper.
BRAIN.md is free and open source, so it beats paid memory services like Mem0 or Cursor's enterprise tiers on price. For solo developers and small teams who don't mind manual upkeep, it's the cheapest way to get persistent AI memory. If you need zero maintenance, you'll pay in time—or money—for an automated alternative.
Setup time & first value
How long it actually takes to get something useful out of Brain.Md — broken out by persona, not the marketing-page minute.
For a solo developer familiar with Node.js, you can install the CLI globally, run 'brain-setup' in an existing repo, and have a basic brain structure in under 5 minutes. For a new project, 'brain-bootstrap' scaffolds the full structure in about 2 minutes. Adding your first truth takes another minute or two. For teams, add 10-15 minutes to review the initial structure and decide on conventions.
Switching to or from Brain.Md
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From README.md/AGENTS.md: Run 'brain-setup' to create the folder structure, then move key notes into pages with 'brain update-truth'.
- →From any Markdown notes: Copy unstructured content into brain pages, then use the CLI to formalize each as a truth.
- ↗To any cloud memory service: Export brain as plain Markdown and manually port key truths into the service's format.
- ↗To a custom memory system: Since the brain is just Markdown, you can script a converter to any JSON or database schema.
Resources & Guides
Tutorials & Learning
Official links
Tools that pair well with Brain.Md
Common stack mates teams adopt alongside Brain.Md, with the specific reason each pairing earns its keep.
Pieces for Developers
AI memory layer that auto-captures your work into a searchable timeline and feeds context to MCP-ready AI tools
Kiro
Spec-driven AI coding platform that turns prompts into tested, production-ready code with parallel agents.
Windsurf
Orchestrate fleets of local and cloud coding agents from one AI-native IDE.
Featured Head-to-Head Comparisons
Brain Md vs Spider Cloud
If you need real-time web data for AI agents or RAG pipelines, Spider Cloud is the obvious choice with its Rust engine, 99.9% uptime, and sub-cent cost per 1k pages. If you're building software with LLM coding assistants and frustration at lost context across sessions, Brain.Md is a free, elegant, file-based memory layer that persists decisions alongside your code. The two tools solve different problems—one feeds data into AI, the other preserves AI's understanding of your project.
Brain Md vs Temporal Ai
For teams building reliable, long-running AI agents or microservices that must survive failures, Temporal AI is the clear choice with its durable execution and extensive SDK support. For solo developers using Claude Code or Codex who want to avoid re-explaining context between sessions, BRAIN.md is a simpler, free, and lightweight solution. Choose based on whether you need fault-tolerant orchestration or persistent memory for coding agents.
Brain Md vs Voyage Ai
Voyage AI wins for enterprise RAG with domain-optimized embeddings and low-dimensional vectors; Brain.Md wins for AI-assisted coding with persistent, versionable memory. If you need accurate retrieval on finance/legal documents, choose Voyage. If you're a developer wanting AI agents to remember project context, choose Brain.Md.
Alternatives to Brain.Md
View allPieces for Developers
AI memory layer that auto-captures your work into a searchable timeline and feeds context to MCP-ready AI tools
Frequently Asked Questions
Best-of guides
Used Brain.Md? Help shape our editorial sentiment research.


