MFS 把代码、文档、issue 都变成 Agent 能搜的文件路径，在 IM 里就能拿到完整上下文，回答更准。去看一下开源项目。
团队发现，同一个 Agent 放在 IM 中比放在终端或独立 Web 应用中使用率更高、答案更好，因为 IM 自带问题、人员、历史决策、链接、截图等上下文。但答案往往还依赖代码、设计文档、GitHub issue、数据库记录等外部来源。MFS 将这些来源映射为稳定的文件路径，让 Agent 能像工程师一样先定位再查询，最终将对话、团队知识与外部工具统一为可搜索的上下文层。该项目已在 GitHub 开源。
We kept seeing the same pattern with agents: when the same agent lived inside IM instead of a termin...
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 💬 0 🔄 0 ❤️ 0 👀 105 ⚡