Agent Memory Bridge
简体中文
Your coding agent should start with the right project context, not a stale dump.
Agent Memory Bridge is persistent project memory for coding agents: a local-first MCP memory layer with SQLite/WAL as the durable store, FTS5 for lexical recall, and an optional local embedding sidecar for semantic or hybrid retrieval. It stores durable repo decisions, gotchas, procedures, and handoffs while keeping short-lived coordination separate.
Codex is the reference workflow, not the product boundary. If a client can launch a local stdio MCP server, it can use Agent Memory Bridge.
Why It Exists
Most agent memory either feels too shallow or too heavy:
- summaries become stale blobs
- vector stores hide why something was recalled
- every new session starts cold or gets a stale context dump
- handoff state turns into ad hoc notes or a queue you did not want to build
AMB takes a smaller path: local SQLite authority, explicit namespaces, inspectable records, benchmarked lexical/hybrid recall, and a signal lifecycle for lightweight coordination.
