How-to

LangChain 创始人分享 agent 维护 wiki 的 curator 模式

Why we picked it

多智能体各自改知识库很容易改乱,Harrison Chase 建议单独跑一个 curator agent 专门负责所有编辑,评论区也有人验证了同样的做法:subagent 只汇报结果,由主 agent 统一写。做 agent 记忆和知识库的同学可以照这个结构试。

LangChain 创始人 Harrison Chase 在 X 上描述了一个多智能体系统中的常见问题:主 agent 和 subagent 都无法可靠地编辑共享知识库 wiki。他提出的解法是引入一个独立的 curator agent,专门负责所有 wiki 编辑操作。

Body

评论区中开发者 himanshutwtxs 分享了类似的实践经验:让多个 subagent 各自编辑 skills 和知识库会迅速变得混乱,因此改为 subagent 只向 orchestrator 汇报执行成功与失败的情况,由 orchestrator 统一做出修改。这一模式将"读"和"写"权限分离,写入集中到单一环节,避免并发编辑冲突。

这种单一写入者的 curator 模式对搭建多智能体系统的开发者有直接参考价值,尤其在 agent 记忆、知识库维护场景中,是 LangGraph 等框架实践中逐步形成的经验共识。

Original · Harrison Chase

This is pretty common pattern we see - agents (whether main agent or subagents) can’t reliably edit the wiki, so you want a separate agent to do all the edits (what I call a curator agent here) hims @himanshutwtxs really like the overall idea, a banger again :) been doing something similar in practice myself. one thing that helped a lot was not letting subagents touch the skills or knowledge at all when each of them edited it, it turned into a mess pretty fast. so now subagents just report back to the orchestrator, and based on what worked and what failed, only the orch makes the changes 🔗 View Quoted Tweet📊 7 ⚡

Industry Coordinates & Source Verification

This report is categorized under AITOP's "How-to" desk, focusing on US frontier AI labs and Silicon Valley technology leaders. Within our cross-regional analytical framework, it directly maps to AI developer toolchains, coding agents, and engineering workflows. Key entities and technical topics under continuous tracking include LangChain, LangGraph, agents, prompt engineering.

Source attribution: curated from Harrison Chase (@hwchase17).