LangChain创始人分享了一个文档管理的小技巧：把智能体工程文档放VCS外面，用FS工具访问，避免分支迷失。
该建议指出，用于智能体工程的计划、研究等上下文文档应放在仓库外，而非版本控制系统中。原因包括：文档无需合并语义，线性历史即可满足99.9%场景；存入仓库将导致文档在不同分支间丢失。推荐系统通过FS工具访问、可发现、可持久化归档且支持协作。该讨论由LangChain创始人Harrison Chase转发，引发对智能体开发最佳实践的思考。
Something we’re thinking a bunch about as well Would love thoughts!
Something we’re thinking a bunch about as well Would love thoughts! dex @dexhorthy context engineering docs for agentic engineering - plans, research, etc SHOULD NOT be stored in version control: A good docs management system keeps them: > outside your repo > accesible to agent via FS tools > discoverable by agent (even just maybe via sysprompt append) > persisted / recoverable / archivable > collaborative (shareable, commentable) why keep them outside the core VCS repo? 1) they don't need merge semantics, just linear history is plenty in 99.9% of cases 2) if they are committed that means they can live on branches, get lost when you change branches, you have to remember where they were, etc etc wdyt? 🔗 View Quoted Tweet 💬 0 🔄 0 ❤️ 4 👀 379 📊 1 ⚡