Open-source project · Agent infrastructure
Agent Memory Bridge
A governed local project-memory layer for coding agents. It keeps a confirmed decision and its reason, so a later session can recall why.
01
What it is
Agent Memory Bridge (AMB) keeps a confirmed project decision and its reason in a local store. A later session gets it back by recalling, not by rereading the old chat.
AMB runs as an MCP server. It is local-first over stdio and does not require a hosted memory service. A Streamable HTTP transport with an HTTP gateway is optional.
02
The problem
Code tells the next session what exists. It does not explain why it is written that way. When the reason lives only in chat history, the next session has to guess.
Remembering more is not the goal. The useful part is knowing where a decision came from, whether it is still current, and how it changed.
03
How it works
- 01BindBind the project.
project initdetects the Git repository and proposes a namespace such asproject:my-app. It does not learn decisions from the tree. - 02StoreStore a confirmed decision.The
storetool saves a claim and its reason. A decision is stored only after it is confirmed. Chat history is not treated as already stored. - 03RecallRecall at the start.The next session calls
recallon purpose, before it changes code. Connecting the server is not enough. - 04ReplaceReplace what changed.A changed decision is revised or superseded instead of silently overwritten. The older record stops surfacing by default and stays in the change history.
- 05InspectInspect what surfaced.
exploreshows what AMB currently knows.inspectshows why a record surfaced. Both are local and read-only.
04
Evidence and limits
- The demo in the README is a local proof: one process stores a decision, and a second process on the same AMB home recalls the same record. The README states that it is not a filmed coding-agent session and not an adoption measurement.
- There is no automatic learning. AMB is not a transcript archive, and it does not promise that an agent will remember everything.
doctorandverifycheck server prerequisites. They do not prove that a client loaded its MCP configuration.- The public surface is 17 MCP tools. Setup, Explore and Inspect stay in the command line.
- Current evidence and non-claims are kept in the repository's Production Status document.
05