Milvus 开源了 MFS，能把聊天、代码、文档全串起来给 Agent 查，不用再手工拼上下文了。
Milvus 团队观察到，当 Agent 运行在 IM 中时用户使用更多且答案更好，但上下文仍缺失代码、GitHub issues、数据库记录等。MFS 为这些来源提供稳定的类文件路径，让 Agent 像工程师一样先定位再检查原始文件。MFS 将对话、团队知识和外部工具转化为 Agent 可搜索的上下文层。项目已在 GitHub 开源。
MFS 01: https://t.co/PVPqlHy7CR
MFS 01: x.com/milvusio/statu… Milvus @milvusio We kept seeing the same pattern with agents: when the same agent lived inside IM instead of a terminal or separate web app, more people used it, and the answers were often better. The reason was not the UI alone. IM already contains the working context: the question, the people involved, the decision history, the links, the screenshots, and the half-finished reasoning that never makes it into a doc. But that context is still incomplete. The answer often depends on code, design docs, GitHub issues, database rows, customer notes, or a debugging session from last week. That is the gap MFS is trying to close. MFS gives those different sources stable, file-like paths, so an agent can move through them the way an engineer would: find likely places first, then inspect the original file, thread, issue, or record before answering. For agentic workflows, this matters. The best interface may be IM, but the best answers need context from everywhere else too. MFS turns conversations, team knowledge, and external tools into one searchable context layer for agents. Repo: github.com/zilliztech/mfs… Your browser does not support the video tag. 🔗 View on Twitter 🔗 View Quoted Tweet 💬 0 🔄 0 ❤️ 0 👀 24 ⚡