想搞懂 agent memory 到底在说啥？这篇总结了5个开源项目，每个侧重点完全不同，直接点出趋势：从存更多转向检索对。
当前 agent memory 被泛化使用，实际有不同含义。codebase-memory-mcp 将 memory 定义为代码库结构（函数、类、调用链）。MemSearch 使用 Markdown 作为事实源，搭配 Milvus 索引实现混合检索与渐进召回。agentmemory 跨 Claude Code、Codex、Cursor 等 6 个客户端跟踪工作空间上下文。Basic Memory 构建人可编辑、代理可搜索的 Markdown 知识库。ai-memory 专注跨供应商工作交接，避免重复解释架构和失败尝试。
Everyone is talking about agent memory, but the term is starting to hide more than it explains. For...
Everyone is talking about agent memory, but the term is starting to hide more than it explains. For coding agents, it is not just “save chat history, embed it, retrieve top-k” anymore. These open-source projects show that “agent memory” can mean very different things: 1. codebase-memory-mcp github.com/DeusData/codeb… Memory as codebase structure: functions, classes, call chains, routes, dependencies, and impact paths. 2. MemSearch github.com/zilliztech/mem… Memory as retrieval infrastructure: Markdown as the source of truth, Milvus as the index, plus hybrid search and progressive recall. 3. agentmemory github.com/rohitg00/agent… Memory as workspace context that follows coding agents across Claude Code, Codex, Cursor, Gemini CLI, OpenCode, and MCP clients. 4. Basic Memory github.com/basicmachines-… Memory as a readable knowledge base: Markdown notes that humans can edit and agents can search. 5. ai-memory github.com/akitaonrails/a… Memory as continuity and handoff, so work can move between agent vendors without re-explaining architecture, failed attempts, and open questions. These projects point to a simple trend: agent memory is moving from “store more context” to “retrieve the right context.” For coding agents, memory is becoming less like a notes file and more like a retrieval layer. 💬 0 🔄 0 ❤️ 1 👀 51 ⚡