AGENTS · 122 POSTS · PAGE 2/13
Agents.
Writing tagged Agents: 122 posts on AI systems, engineering tradeoffs, and building products that have to work in production.
An audit of nine Claude Code spec-driven features found 75.3% of reviewer tokens went to re-reviews, and the orchestrator that checked its own work stopped 4 of 11 flagged rounds.
On 181 failed bug-fix attempts, a model-written lesson matched the raw transcript (−1.7 points), and gains shrank once the full test suite was checked. Skip the distillation call until you measure it.
Malicious memory files moved secure-code rates only −8 to +6 points across three agents, but only 4 of 18 sessions that called the file an attack said so in the final message.
Across 5,625 trials, coding agents followed local repo precedent over conflicting instructions; one written rule in CLAUDE.md fixed it 59 of 60 times where a code example managed 38.
Giving agents program structure as code-like stubs cut relative test error by 48.4% versus the best behavioral specs, and let a model 15–26× cheaper land within 5–8 points of the large one.
A harness cut 3,827 of 11,189 tool results into broken JSON while using 5.75% of the context window. If your agent seems oddly blind, audit truncation before blaming the model.
Across 147,002 coding-agent traces, early-failure predictors were at chance within a task (AUC 0.50), and plain continuation beat restart on solve rate and cost. Don't abort on prefix signals.
Across 3,000 turns, five models in Codex and Claude Code churned up to 31x the original code, and often kept editing after declaring the task done. Cap loops by diff budget, not the agent's verdict.
Deleting old turns rarely hurt SWE-bench results, but agents re-fetched what was removed, and under cache-aware pricing none of 42 setups got cheaper.
Agents reached sufficient evidence of a blocker in 98.6% of runs, then kept working. A simple escalation tool and a harness monitor cut wasted steps and unsafe requests.