Skip to content

Brain-AI Memory v0.5.0 — Project Memory That Survives the Next Session

Choose a tag to compare

View all tags
@Hahyun-Lee Hahyun-Lee released this 16 Jul 00:13
v0.5.0
e8fed84

Project memory that survives the next session

Brain-AI Memory v0.5.0 turns an existing MEMORY.md into reviewed,
project-scoped memory that an MCP host can recall, update, checkpoint, and
resume. The source file stays untouched, replaced facts keep their history, and
exact state no longer has to be guessed from prose.

What is new

  • Audit a Markdown memory file before anything enters the typed store.
  • Approve, apply, and logically roll back imports with file-and-line provenance.
  • Keep project-bound memory, rules, state, and handoffs out of other projects.
  • Write preview-first project MCP configuration for Codex or Claude Code.
  • Resume the latest handoff after a fresh MCP process starts.
  • Inspect local operation without an API key, hosted service, or database server.

Verified release path

  • 64 public software tests.
  • Python 3.10, 3.11, and 3.12 compatibility checks.
  • Clean-wheel audit → review → apply → generated Codex MCP configuration → real
    stdio tool calls → checkpoint → fresh process → resume.
  • Runtime contract: 14/14; component contracts: all-ten 20/20 versus flat 1/20.

These are software and integration results. They do not claim that Codex or
Claude Code will always choose the tools, or that this release improves LLM
answer quality over RAG or long context.

Try it

git clone --branch v0.5.0 --depth 1 https://github.com/Hahyun-Lee/brain-ai-memory.git
cd brain-ai-memory
python3 -m venv .venv
source .venv/bin/activate
python -m pip install ".[mcp]"
brain-ai --home "$(mktemp -d)" tour

Then follow the adoption workflow
or the 한국어 README.

Use it when work spans many sessions, facts or state keep changing, and a stale
or cross-project memory can cause a real mistake. For a short one-off task, a
plain MEMORY.md is still the simpler choice.

Assets 4
Loading