{"slug": "less-context-fewer-ai-hallucinations", "title": "Less Context, Fewer AI Hallucinations", "summary": "A developer describes a three-agent code-review setup that reduces AI hallucinations by stripping the original reasoning from the reviewer's context and giving it only checkable claims plus the source material. The approach draws on research including Google DeepMind's finding that LLMs largely cannot self-correct without external feedback, NeurIPS 2024 work showing models favor their own outputs, and Chroma's 2025 Context Rot report, which found 18 frontier models grew less reliable as input length increased. The author recommends using a different model family for verification and capping correction loops at one or two rounds.", "body_md": "*Originally published on [Chirpper](https://chirpper.com/p/3f6f4d4c/less-context-fewer-ai-hallucinations).*\n\nEveryone is trying to figure out how to give AI more context so it hallucinates less: bigger context windows, more retrieval, longer prompts, entire codebases pasted in. Sometimes less context is better. When you’re asking AI to check work for mistakes, it nearly always is. Here’s why.\n\nThe assumption is that more input means better output. The research says otherwise.\n\nStanford’s “Lost in the Middle” study found that model performance drops as input gets longer, even for models built for long context. Chroma’s 2025 “Context Rot” report tested 18 frontier models, including GPT-4.1, Claude 4, and Gemini 2.5. All of them got less reliable as input length grew, even on simple tasks.\n\nA bigger context window is a bigger space for the model to get lost in.\n\nThe most common advice for catching AI mistakes is to ask the model to “double check your work.” That usually means the same model, in the same conversation, with all of its original reasoning still sitting in context.\n\nIn 2024, Google DeepMind researchers tested whether large language models can correct their own reasoning without outside help. Mostly, they can’t. Without external feedback, models struggled to fix their mistakes, and sometimes they did worse after “correcting” themselves. (Huang et al., ICLR 2024)\n\nThere’s also a bias problem. A NeurIPS 2024 paper by Panickssery, Bowman, and Feng found that LLMs rate their own outputs higher than equally good text from other models or from people. The models can also recognize their own writing, and the better they are at recognizing it, the stronger the bias.\n\nSo a checker that can see everything has two problems. It’s anchored to the original reasoning, and it’s working in a degraded context window. It’s grading its own homework with the answer key it wrote.\n\nHere’s the setup I use for code review:\n\nAgent 3 never sees how Agent 1 reached its conclusions. It only sees the claims and the source material, so it can’t be talked into agreeing. It has to check.\n\n**Strip the reasoning, keep the source.** “Less context” doesn’t mean less information. The DeepMind finding is that self-correction fails *without external feedback*. The code, the document, or the dataset is that external feedback. Remove the author’s argument, not the ground truth.\n\n**Turn output into checkable claims.** “Is this review good?” is a vibe check. “Is it true that this function never handles a null input?” can be verified. The extraction step in Agent 2 does most of the work.\n\n**Use a different model for verification when you can.** The self-preference research suggests a fresh instance of the same model may still favor text that sounds like its own. A different model family reduces that.\n\n**Cap the loop.** One or two correction rounds usually catch what matters. “Repeat until perfect” burns tokens and can create new problems.\n\n**Spend it where it counts.** Anthropic reported that its multi-agent research system beat a single agent by 90.2% on its internal research eval, but at roughly 15 times the tokens of a normal chat. That’s research rather than code review, but the tradeoff is the same. Use this for output where a wrong fact is expensive, not for every prompt.\n\nNone of this is new. It’s why developers don’t QA their own code and writers don’t copyedit their own books. The person who made the thing is too close to it.\n\nAI just makes the principle easy to apply. Spinning up a reviewer with clean context costs one more prompt. Give it the facts, hide the reasoning, and let it check.\n\n**Sources:** \n\nHuang et al., “Large Language Models Cannot Self-Correct Reasoning Yet”; \n\nPanickssery, Bowman & Feng, “LLM Evaluators Recognize and Favor Their Own Generations” (NeurIPS 2024); \n\nLiu et al., “Lost in the Middle” (TACL 2024); \n\nHong, Troynikov & Huber, “Context Rot” (Chroma, 2025); Anthropic, “How we built our multi-agent research system” (2025).", "url": "https://wpnews.pro/news/less-context-fewer-ai-hallucinations", "canonical_source": "https://dev.to/richardkersey/less-context-fewer-ai-hallucinations-10l7", "published_at": "2026-11-20 21:09:13+00:00", "updated_at": "2026-11-20 21:14:52.902889+00:00", "lang": "en", "topics": ["large-language-models", "ai-agents", "ai-tools", "ai-research"], "entities": ["Google DeepMind", "Chroma", "Anthropic", "Stanford", "NeurIPS", "GPT-4.1", "Claude 4", "Gemini 2.5"], "also_reported_by": [], "takeaway": "For AI code review, hide the original reasoning and pass only extracted claims plus source material to a fresh reviewer, ideally from a different model family, and cap correction at one or two rounds.", "recommendation": {"advice": "When verifying AI-generated work, give the checker only the claims and source material, not the original reasoning, and use a different model family to avoid self-preference bias.", "playbook": "output-verification", "playbook_url": "https://wpnews.pro/playbooks/output-verification"}, "alternates": {"html": "https://wpnews.pro/news/less-context-fewer-ai-hallucinations", "markdown": "https://wpnews.pro/news/less-context-fewer-ai-hallucinations.md", "text": "https://wpnews.pro/news/less-context-fewer-ai-hallucinations.txt", "jsonld": "https://wpnews.pro/news/less-context-fewer-ai-hallucinations.jsonld"}}