Fetching from the wire…
Top 5 · 2026-05-26 · source-backed
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 success rates by 0.5-2% AND increased inference costs by over 20%.
Read that again. Having the AI write its own instructions made it perform worse and cost more.
I've been maintaining my own CLAUDE.md for months now, and this confirms what I noticed empirically. The entries that work are the ones I wrote after watching Claude make the same mistake three times. "Don't mock the database in integration tests." "Always check if the branch exists before creating it." "Use WAL mode for all SQLite connections." Each one traces back to a real failure. They're specific, opinionated, and born from pain.
The entries that don't work are the speculative ones. "Consider edge cases carefully." "Follow best practices for error handling." That kind of generic guidance is what LLMs generate when you ask them to write context files. It sounds reasonable but doesn't change behavior. Worse, it bloats the context window, which means the actually useful rules get less attention.
The study also confirmed something I'd suspected about Claude Code's extension mechanisms: MCP servers, plugins, skills, and hooks all operate at different points of the agent loop with different context costs. Knowing which lever to pull matters. A hook that preprocesses output is cheap. An MCP server that's always loaded is expensive. Choose accordingly.
What builders should do: Stop auto-generating CLAUDE.md files. Write entries only when you encounter a repeated agent mistake. Keep them short, specific, and grounded in observed failures. If you haven't seen the failure three times, you don't need the rule. Delete any speculative guidance. Your context budget is finite. Spend it on rules that actually change behavior.
Each link below shares sources, entities, or timing with this story.
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...
1. Set package cooldown to 72 hours across all your package managers. pnpm: resolution-time=72h, uv: --exclude-newer, npm via .npmrc. This single config change would have protected you from the LiteLLM attack. Willison's survey covers all seven managers. 2. Install Lasso Secur...
1. Use claude agents --json to build session dashboards. Claude Code v2.1.145 outputs all live agent sessions as structured JSON with status, model, elapsed time, and parent relationships. Pipe it into a tmux status bar widget or session picker script for switching between bac...
Addy Osmani's O'Reilly CodeCon talk, published March 26, gives us the first real empirical data on multi-agent coding that I trust. Not vendor benchmarks. Not cherry-picked demos. Controlled measurements across real development tasks. The headline finding: three focused agents...
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...
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 reduc...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.