Weaviate出了个视频，把Agentic RAG拆成5个系统讲透了，不是吹大窗口，而是教你怎么控制上下文，推荐搞RAG的人看看。
Weaviate发布的视频指出，更大的上下文窗口无法解决有问题的Agentic RAG管道。长上下文会引入矛盾信息、掩埋相关工具并导致后续输入被忽略。视频将生产级Agentic RAG拆分为5个系统：查询增强（翻译模糊或多部分输入）、检索（选择平衡精度与上下文的块策略）、记忆（分离短期上下文与长期记忆）、工具（提供清晰描述和schema）和代理（决策编排层）。每个环节都需精心设计上下文工程，而非仅靠扩大窗口。
A bigger context window won't fix a broken agentic RAG pipeline. Long contexts can introduce contra...
A bigger context window won't fix a broken agentic RAG pipeline. Long contexts can introduce contradictory information, bury relevant tools, and cause later inputs to be ignored. Every retrieved chunk, tool output, instruction, and conversation turn competes for the model's attention. This is why production agentic RAG is really a 𝗰𝗼𝗻𝘁𝗲𝘅𝘁 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 problem: controlling what information reaches the model, when, and in what form. In our newest Youtube video, @victorialslocum breaks down the five systems that make up an agentic RAG pipeline: 1️⃣ 𝗤𝘂𝗲𝗿𝘆 𝗔𝘂𝗴𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻 - translating vague, misspelled, or multipart human input into something retrieval and downstream tools can actually use 2️⃣ 𝗥𝗲𝘁𝗿𝗶𝗲𝘃𝗮𝗹 - choosing a chunking strategy that balances precision with enough surrounding context. Small chunks can lose meaning; large chunks consume context and produce noisier embeddings. 3️⃣ 𝗠𝗲𝗺𝗼𝗿𝘆 - separating active short-term context from externally stored long-term memory. Dumping the full conversation history into every request just lets stale details compete with current information. 4️⃣ 𝗧𝗼𝗼𝗹𝘀 - giving the model clear descriptions, schemas, and access to the right tools at the right stage. Many tool failures are actually context engineering failures in disguise. 5️⃣ 𝗔𝗴𝗲𝗻𝘁𝘀 - the decision and orchestration layer connecting everything above. Agents can reformulate queries, select tools, evaluate results, and change strategy, but they also compound every upstream context failure. A better prompt can't repair irrelevant retrieval, contr youtu.be/sUoNoaatRvU?si… ool the model can't find. The video: https://t.co/M9I9WKbOjL 💬 0 🔄 0 ❤️ 3 👀 143 📊 1 ⚡