I stopped fighting the model and built a memory system around it instead. I kept hitting the same wall: spending 20 minutes reloading context at the start of every session. Paste the roadmap, paste the open issues, explain what we were debugging yesterday. By the time Claude was caught up, I was drained before I'd written a line. So I stopped treating Claude as the product. I started treating the context around Claude as the product. 7 tools. 6 memory types. One working environment: - Claude Code runs in the repo. Sees files, sees commits, holds working memory for the current task. - Claude Cowork sits above it. Orchestrates across projects when I'm not in a single repo. - Neo4j with the Neo4j MCP server holds semantic memory. Entities and relationships. Claude queries the graph before answering anything strategic. - Claude-Mem logs every session as a "change" with facts and narrative. I scroll it like a changelog of my own thinking. Last week's session #621 still shows me the exact HreflangMeta fix I pushed. - Obsidian is the long-term knowledge base. Hundreds of notes. Agent Skills docs, API references, project dossiers, all linked in a graph view Claude can read as plain files. - Custom Skills hold procedural memory. "How I write for 15 platforms." "How to set up a new HubSpot client." Written once, triggered by description match when relevant. - MCP Servers give Claude capability memory. Pinecone, Supabase, Vercel, HubSpot, Neo4j — not tools I re-explain, tools he can just call. The result is the part that surprised me. Claude now catches patterns I miss. "You abandoned this approach 3 weeks ago and the reason was the Supabase async mismatch." Things I wouldn't have remembered. That's the real unlock. Not smarter answers. A coworker with memory.
7 个工具 6 种记忆类型：让 Cowork 当总指挥，Claude 终于不再每天失忆
作者不再试图让 Claude 本身变聪明，而是在它周围搭了一整套记忆系统：Claude Code 在单个仓库里干活、Claude Cowork 跨项目统筹，Neo4j（语义图）+ Claude-Mem（会话变更日志）+ Obsidian（长期知识库）+ 自定义 Skills（流程记忆）+ MCP 服务器（能力记忆）六种记忆并行。结果是 Claude 开始帮他发现自己都忘了的模式——「三周前你放弃过这个方案，原因是 Supabase 异步不匹配」。作者形容这是「有记忆的同事」而非「更聪明的回答」
Developer who built a 7-tool memory stack around Claude to solve session amnesia
使用场景
3 个月前，作者每次开新会话都要花 20 分钟粘贴路线图、未关闭的问题、前一天调试到哪一步。等 Claude 跟上节奏，他本人已经精疲力尽，一行代码还没写。他意识到问题不在模型本身——模型换哪个都一样失忆。真正要做的是把上下文/记忆当成产品，在 Claude 外面搭一整套基础设施。
提示词
Before answering anything strategic about this project, do three lookups: (1) query the Neo4j semantic graph for entities + relationships relevant to the question, (2) grep the Claude-Mem session log for related past decisions and their reasons, (3) scan Obsidian notes for long-form documentation of the area. Surface any prior decision we made that contradicts or supports the current plan — quote it with the session number or note link. Then proceed.
预期结果
作者搭出了一套 7 工具 / 6 记忆类型的栈，Cowork 担任跨项目调度器： - **Claude Code**：仓库内工作记忆（文件、提交、当前任务） - **Claude Cowork**：跨项目总指挥，不在单一仓库时由它调度 - **Neo4j + MCP**：语义记忆（实体和关系），战略性问题先查图 - **Claude-Mem**：会话变更日志，每次会话记成一条「change」，像读自己的变更日志一样回顾 - **Obsidian**：长期知识库，几百条笔记，图谱视图 Claude 可直接读 - **自定义 Skills**：流程记忆，比如「15 个平台各怎么写」「HubSpot 新客户开户流程」 - **MCP 服务器**：能力记忆（Pinecone / Supabase / Vercel / HubSpot / Neo4j），不用每次解释，直接调用 **意外收获：** Claude 开始反过来提醒他——「这个方案你三周前放弃过，原因是 Supabase 异步不匹配」——那些他自己都不记得的东西。作者总结：真正的突破不是更聪明的回答，而是终于有了一个「有记忆的同事」。