The Repo Is the Context: Why Agents Don’t Need History
Dev.to / 6/19/2026
💬 OpinionIdeas & Deep AnalysisModels & Research
Key Points
- The author argues that while history (ADRs, specs, migration logs, planning docs) is valuable for humans to understand “why” systems evolved, it should not be the default context for coding agents making edits to the present system.
- Coding agents like Claude Code and Codex should primarily read the current source of truth—current schema, module boundaries, public APIs, tests, configuration, state machines, and dependency rules—rather than replaying outdated documents.
- The article highlights a concrete failure mode: agents can confidently perform wrong actions by obeying stale documentation from months ago, which is not hallucination but “obedience to history.”
- It frames token/context selection as a “what do you hand over” problem: each token should provide verified, current facts, not guesses derived from historical narrative.
- The core distinction is that history explains “why,” while the present source of truth explains “what,” and each serves different readers and different tasks.
Continue reading this article on the original site.
Read original →Related Articles
Testing Mythos and Fable, Moving Beyond SWE-bench, Nvidia's Open Contender
The Batch

Scout Pre-Beta: Hopes & Expectations
Reddit r/artificial
I Saved $2,620 Monthly Ditching GPT-4 — A Data Scientist's Deep Dive
Dev.to
How to Start an AI API Affiliate Business in 2026: A Growth Hacker's Playbook
Dev.to

Building a Women-First AI Boyfriend App: What We Learned
Dev.to