Fetching from the wire…
Top 5 · 2026-04-08 · source-backed
ETH Zurich researchers ran the first serious study on context files for AI coding agents. 5,694 pull requests across 138 repositories, tested with three frontier models: Sonnet 4.5, GPT-5.2, and Qwen3-30B. The finding that caught me off guard: LLM-generated context files reduced task success by 3% and added 2-4 extra reasoning steps per task, increasing inference costs by more than 20%.
Human-curated files did slightly better. A 4% improvement. But with the same token overhead, and that overhead compounds across hundreds of agent invocations per day.
The recommendation is specific enough to act on today: keep context files under 60 lines. Limit content to details the model genuinely can't infer from the codebase itself. Custom build commands, non-standard test runners, project-specific naming conventions. And never auto-generate them with an LLM.
This validates something I've noticed in my own setup. My CLAUDE.md is tightly scoped: architecture overview, code conventions, file locations, testing commands. No AI-generated prose. No "detailed guidelines." The temptation to dump everything the agent might need into one file is strong, but the ETH study shows it creates noise that degrades performance.
The connection to harness engineering is direct. Context files are part of your harness. A bloated, auto-generated context file is like giving a contractor a 50-page specification when they needed a one-page brief. The model spends tokens processing irrelevant context instead of solving the actual problem.
An r/ClaudeAI post (51 upvotes) from the same day made the same argument from a practitioner angle: "context anxiety," agents losing track of what they're doing, is better solved by a well-structured CLAUDE.md than by adding more coordination layers. The academic data and the community wisdom converged.
If you have an AGENTS.md or CLAUDE.md over 60 lines, today's the day to cut it. Strip it to what the model can't figure out on its own. Your agents will work better and cost less.
Each link below shares sources, entities, or timing with this story.
Stop auto-generating your context files. The data says they're actively hurting you. ETH Zurich tested Claude 3.5 Sonnet, GPT-5.2, GPT-5.1 mini, and Qwen Code across 138 real-world Python tasks and found that LLM-generated context files (AGENTS.md, CLAUDE.md) consistently degr...
A Reddit post about giving Claude Code a cheap coworker hit 1,123 upvotes and 115 comments on r/ClaudeAI. Read together with the Uber story above, this is the demand signal paired with its solution. The setup: route routine implementation work to a $0.02/call model (Gemini Fla...
1. Flip your multi-model pipeline to review-then-generate. Instead of using a reasoning model to plan before code generation, let the specialist generate freely and use reasoning tokens for review. Paper shows 90.2% pass@1 vs 87.2% for the planning pattern. Source 2. Audit you...
An ArXiv study analyzing Claude Code's design space found something that should make every "auto-generate your context files" workflow uncomfortable. Human-curated CLAUDE.md files improved task success rates by roughly 4 percentage points. LLM-generated CLAUDE.md files reduced...
Accuracy drops 30–50% well before you hit the documented context limit. Not at the limit. Before it. Cross-model testing across GPT-4.1, the Claude 4 family, Gemini 2.5, and Qwen3 quantified what everyone shipping long-context features has felt and couldn't measure (Glasp). Th...
Spotify's Portal team published Xirp on August 10: a vendor-neutral agentic development environment that manages concurrent sessions across Claude Code, Gemini CLI, and Codex, each session isolated in its own git worktree so dozens of agents can work the same codebase without...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.