retrieval augmented generation
394 articles · 15 co-occurring · 10 contradictions · 57 briefs
Article explicitly identifies RAG as 'Foundational Pattern' and dedicates section 2.1 to it; discusses RAG vs fine-tuning decision framework.
PEEK outperforms RAG baselines, suggesting pure RAG isn't optimal; hybrid bounded caching + retrieval is superior
[STRONG] "This nuance hasn't trickled down to retrieval though. Fascinating benchmark that puts a fine point on a bottleneck facing AI systems." — Article identifies retrieval/IR as a critical bottleneck where nuance understanding lags, challenging assumptions about retrieval system capabilities.
Article explicitly differentiates context engineering FROM RAG, suggesting CE is broader/different scope than retrieval strategy alone
Article claims expanded context windows 'eliminate many retrieval workarounds,' but this conflicts with practitioner experience that RAG remains essential for enterprise scale and domain specialization
Suggests that perfect retrieval alone (more documents) can degrade performance—RAG strategies must include filtering, compression, or ranking to manage context length.
[DIRECT] "retrieval work... is a substitute for the real problem of continual learning" — Article frames RAG (retrieval work) as a band-aid solution that masks the deeper need for systems with actual continual learning capability
[STRONG] "A replacement for RAG... Instead, it's the layer that makes context and tools portable, discoverable, and manageable." — Article explicitly clarifies that MCP is complementary to RAG, not a replacement, positioning it as a different layer (integration/portability vs. retrieval mechanism).
Title positions context engineering as superior alternative to standard RAG, suggesting the article contrasts these approaches
Author explicitly notes they didn't need 'fancy RAG' at this scale, suggesting simpler structured approaches can work when context is well-managed
[inferred] "If your AI is modifying large number of files for small changes near the end of a project, you have a serious problem." — Article argues that AI systems modifying many files for small changes indicate a failure state, contradicting the assumption that AI code generation alone ensures project health.
Article explicitly identifies RAG as 'Foundational Pattern' and dedicates section 2.1 to it; discusses RAG vs fine-tuning decision framework.
Claude Context implements RAG specifically for codebases: semantic indexing + dynamic retrieval injected into context.
Paper explicitly tests how retrieval method (sparse, dense, hybrid, graph-based) affects context quality and downstream LLM performance in RAG systems.
RAG (Retrieval-Augmented Generation) — RAG improves generative AI by retrieving relevant external data from open sources (like the internet) or closed systems (like internal databases). This grounds A
Detailed explanation of RAG as solution to contextual distraction, treating conversation history as searchable database
It's RAG on steroids... ADAPTIVE RETRIEVAL: The AI literally asks itself 'Do I need to Google this, or do I already know?'" — The article explicitly positions Deep Research as an evolution of RAG, add
Knowledge Integration (RAG): Retrieving the right document chunks from a vector database at the right time, without overloading the context window." — Article explicitly identifies RAG as a practical
Author identifies RAG as incomplete and proposes the missing context layer that RAG systems need
Effective context engineering here relies on retrieval-augmented techniques like using vector search, RAG, or other filtering methods to inject only the most relevant facts, tools for the current task
Survey explicitly identifies RAG as one of three sophisticated implementations integrating foundational context components. RAG is a primary pattern for context retrieval + processing.
RAG is explicitly discussed as one of two primary architectural approaches
Article explicitly lists RAG systems as part of the 'data plane' of context engineering, identifying retrieval strategy as one of three core pillars.
RAG is explicitly mentioned as one of the core mechanisms within context engineering, representing a specific implementation pattern for information selection and injection.
The entire article is about improving RAG systems by better managing document context upstream
Article positions context engineering as the natural evolution of RAG, showing how retrieval becomes one tool in an agentic loop rather than a pipeline stage.
Article explicitly positions CE as 'far beyond traditional RAG' to include hybrid retrieval, knowledge graphs, and dynamic assembly—showing evolution of RAG concept
Episode explicitly discusses RAG and the importance of separating retrieval from generation as a production pattern
when retrieval breaks down, the language model doesn't compensate. It generates with plausible-sounding content that has no grounding in fact." — Research shows retrieval quality directly determines R
Hybrid search, combining lexical precision with semantic understanding, is the most powerful way to surface that context." — Hybrid search (lexical + semantic) is presented as the solution for surfaci
RAG is explicitly presented as a concrete implementation pattern for solving context bottleneck through retrieval precision
PageIndex is a new RAG approach, directly exemplifies alternative retrieval strategies
Agentic RAG upgrades the traditional "retrieve-generate" single-pass pipeline into an intelligent agent architecture with planning, reflection, and self-correction capabilities, improving the faithful
Article discusses RAG as primary application domain where context poisoning occurs; retrieval layer is attack surface
RAG is explicitly discussed as 'the single most common AI Engineering project at every company in 2026.' RAG is a specific instantiation of the FTI chassis where feature pipeline = retrieval system, t
58 pages of distilled methods and system designs make this a must-read for anyone working with LLM pipelines, RAG systems, memory architectures, or multi-agent frameworks." — Article explicitly identi
Article explicitly discusses RAG as major architectural pattern, focusing on retriever fetching context and generator conditioning on it
Course explicitly teaches RAG as foundation before advancing to memory-enhanced agents. RAG is the retrieval layer of the context engineering pattern demonstrated.
Claude Context implements RAG pattern specifically for codebase retrieval—indexing structured knowledge and enabling semantic search rather than passing raw files.
Article explicitly mentions RAG as a technique for managing context by surfacing relevant information on-demand rather than cramming everything upfront
retrieve the most relevant content using retrieval augmented generation. Tools like LangChain and LlamaIndex orchestrate this process, ensuring token efficiency and building dynamic contexts." — Artic
Paper uses Elicit-powered semantic retrieval as explicit component to inject domain knowledge, demonstrating RAG as context engineering technique rather than generic tool.
The paper directly addresses how retrieval output composition affects LLM performance, identifying distractor quality as a critical RAG bottleneck beyond just retrieval ranking.
building reliable RAG (retrieval-augmented generation) setups, vector databases, knowledge gateways, tool adapters, and long-term context buffers" — Article cites RAG as concrete technical implementat
Retrieval layer explicitly mentioned as architectural requirement; RAG is primary pattern for implementing this.
RAG orchestration tools manage the pipeline that prepares your knowledge base and queries it effectively at runtime, so your agents generate grounded and accurate responses. These tools give you contr
Asking an LLM a question without RAG is like asking someone to respond with the first thing that comes to mind, it just responds what it knows from training data an it may hallucinate. In the other ha
RAG bridges this gap. It's the most commonly deployed AI engineering pattern in production, and it's the first real skill that separates "I played with ChatGPT" from "I built an AI product."" — Articl
RAG is presented as a core context engineering technique for integrating external knowledge during generation, directly addressing the DSL context challenge.
I take messy knowledge, structure it, and connect it to tasks so agents can move faster with fewer mistakes" — Nicolas explicitly works on RAG patterns and demonstrates the practice of structuring kno
RAG is explicitly mentioned as core focus; directly implements context retrieval and injection patterns
Core technique used; knowledge graph-based RAG is a specific instantiation with emphasis on relationship preservation
RAG is explicitly listed as a core topic in the curriculum; represents context retrieval and composition pattern.
Retrieval-augmented generation (RAG) retrieved context: The collection of document chunks retrieved by the retrieval step of a RAG system as being the most relevant to the user prompt." — Article expl
Proposes 'agentic RAG' as an extension of standard RAG by introducing agent-based routing and specialization
Evals are the foundation that power the harness hill-climbing process. Here are the practical ways we source, curate, and use them." — Article demonstrates practical evaluation framework for autonomou
Article's primary focus is implementing RAG using LangChain. RAG is a core context engineering pattern for managing external information injection.
[direct] "Wrong documents were retrieved. Right documents were never ingested. Conflicting snippets from different time ranges were shown together." — Article adds nuance to RAG by identifying specifi
This article directly addresses which retrieval strategy works best in RAG pipelines—a core RAG implementation concern
Article explicitly names RAG as a primary technique for handling large knowledge bases within context constraints
Parent-document retrieval is a specific RAG implementation pattern optimizing the retrieval component
Get daily briefs + MCP graph access.
Subscribe free →