- Guides
Straight answers about agent memory.
Short reference pages for the questions that come up before a team commits to a memory layer. Each one answers the question first and explains the mechanism second.
Start with whichever one you are actually asking.
- What is AI agent memory?
- The state an agent carries between runs — decisions, constraints, preferences, and outcomes — and the operations that keep it correct over time.Read the answer
- Why isn’t vector memory enough?
- Similarity search retrieves text that looks related. It cannot tell you who wrote a fact, where it came from, what it replaced, or how to undo it.Read the answer
- What is an MCP memory server?
- A Model Context Protocol server that exposes memory operations as tools, so any MCP-capable client can commit and recall state without custom glue code.Read the answer
- How do you roll back an agent memory write?
- Snapshot before a risky run, inspect the diff afterward, and roll back the known-bad state instead of hand-cleaning rows.Read the answer
- How do you audit what an agent remembered?
- Keep the operational record attached to the write — which run, tool, or operator produced it, and what it replaced.Read the answer
- See it in the client you already use.
- Bilinc connects through MCP, the Python SDK, or the CLI. The integration guides cover Claude Code, Codex, Cursor, opencode, and any MCP-capable runtime.Coding agentsMCP setup