← Frank Zhang

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

  1. BindBind the project.project init detects the Git repository and proposes a namespace such as project:my-app. It does not learn decisions from the tree.
  2. StoreStore a confirmed decision.The store tool saves a claim and its reason. A decision is stored only after it is confirmed. Chat history is not treated as already stored.
  3. RecallRecall at the start.The next session calls recall on purpose, before it changes code. Connecting the server is not enough.
  4. ReplaceReplace 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.
  5. InspectInspect what surfaced.explore shows what AMB currently knows. inspect shows why a record surfaced. Both are local and read-only.

04

Evidence and limits

05