
My coding-agent sessions have become much more token-heavy over the last year. I now ask agents to inspect the repository, run checks, compare approaches, and revise the work instead of stopping at the first plausible answer. The part I most want to keep from that extra work is what happens after an agent makes a mistake.
When the miss is specific and likely to recur, I try to put the correction into the harness around the next run. I think of that as farming the mistake.
Keeping the correction
A correction can become a clearer prompt, a test, a grader rule, a skill note, or a required check. Where it belongs depends on the failure. An ambiguous instruction should be clarified near the task. Incorrect behavior that passed should become a test. A polished answer that misses the requested point may need a grader.
This post produced that last kind of correction. An earlier draft turned the idea into generic advice about knowing when to stop a long session. The prose was clean, but it answered a neighboring question. I changed the blog workflow so a fresh grader receives the stated takeaway with the draft and checks whether the title, excerpt, body, and ending preserve it.
Not every miss deserves a new rule. Some are local judgment calls, and every harness change adds context and maintenance. I keep the corrections I can describe precisely and expect to need again. The transcript can then disappear without taking the useful part of the correction with it.
Getting closer to one shot
I would love to reach a point where I can one-shot every task I give an agent. That is an aspiration, not a description of how the work goes today. Ambiguous and unfamiliar tasks still need judgment, and even familiar work can fail in a new way.
Farming mistakes is how I try to move toward that goal. When a useful correction becomes part of the harness, the next run starts with something the previous run taught me. Over time, I want the system to make fewer old mistakes so I can spend more attention on the new ones.
Get new posts by email
Occasional updates when I publish something new.
Follow.it sends the emails and includes an unsubscribe link.
Related posts
Make Internal Tools Cheap to Try
February 28, 2026
A lightweight intake form, spreadsheet cleanup script, or dashboard mock can make an internal workflow concrete before it needs production engineering.
Codex for Site Edits, Sora for Visual Sketches
February 22, 2026
Codex helps me make small site edits from my phone; Sora remains a way to test visual directions before I know whether they belong.
Planning and Verification in AI-Assisted Coding
February 3, 2026
My AI-assisted coding workflow now uses short briefs, plan reviews, checkpoints, and build/lint/test verification.