Current Edition · 2026.07

The Field Guide
// Coding with Agents

Fifteen months of workshops. Three generations of agent tooling. The tools kept changing; the operating principles didn't. What you're holding is the distilled result — the lessons that survived — split into two layers: durable directives that outlived every tool migration, and a versioned command console where every snippet carries a stamp proving it was re-checked against the CLIs actually installed today, not remembered from a slide.

15 workshops · Mar 2025 → Jun 2026 Cursor → Claude Code → Codex re-stamped 2026-07-10
Eggo the mission commander on a starship bridge, one mitten on a glowing holographic manual whose pages float as neon panels
mission briefing // orbital deck

The tools are disposable. The lessons are the equipment.— the whole guide, in one sentence

Eggo leaning over a floating command card with a comically large magnifying glass, hugely enlarging its verification seal

§0How to read the stamps

Every command in this guide was re-run against currently installed tooling on the stamp date — not copied forward on faith. Muscle memory is a liability in a field that reinvents itself quarterly; the stamp tells you exactly how much to trust yours.

StampMeaning
verified 2026-07-10Type it as written. Probed against the live CLI on the stamp date.
changedStill works, but the surface moved — read the note first.
riskyVerified, but explicitly dangerous. Isolation + external verification required.
supersededThe concept survives; the entry point moved. The note names the current equivalent.
removedGone. Kept for archaeology; the note names the nearest replacement.

Stamps older than ~3 months are a smell. The whole reference is re-verified by an automated probe suite before every workshop — details at the end of the Command Console.

§1How coding with agents evolved

These lessons weren't designed — they were forced, one era at a time. Each era below ended when its favorite habit hit a wall. Knowing the arc helps you recognize which era you're operating in right now:

01

Spring 2025 — Control the evidence

The agent lives inside the editor and follows instructions. The human's edge is supplying reality: official scaffolds, curated files, search results, real examples, tests. "Context engineering" becomes a deliberate craft — the agent performs only as well as the evidence it can see.

02

Aug–Sep 2025 — The agent becomes a process

Print mode, JSON streams, pipes, shell functions, tool allowlists, hooks. The agent stops being a chat window and becomes a Unix process you can wrap, compose, and reuse. Plan in one context, execute in another. Convert every repeated success into a named tool.

03

Oct–Nov 2025 — Orchestration hits its limits

Fan-out is easy; reviewing the fan-out is not. Human attention doesn't scale with token spend. Overlapping agents create merge debt. More context can make results worse. The correction: normal code, explicit task boundaries, small commits, one or two supervised tracks.

04

Dec 2025 — Consolidation and taste

Keep foundational instructions thin. Load specialized guidance only when relevant. Enforce invariants with hooks, not prose. Generate alternatives with councils — but reserve the final choice for human taste. Treat agent-built infrastructure as a sandcastle until its value earns durability.

05

2026 — Contracts and receipts

The destination: disposable implementation under a durable human contract. Requirements, decisions, constraints, and proof scenarios outlive any individual chat. A coordinator holds the goal; narrow workers get bounded contexts; saved checks — not agent narration — establish completion.

Chapters

Eggo the inspector ignoring a robot's holographic thumbs-up and taking the physical receipt tile printing from a verification kiosk

⚠The one rule above the rules

An agent saying "done" is not evidence. Completion is established by a saved, inspectable artifact outside the conversation — a passing test run, a diff, a log, a screenshot, a receipt.

No saved check, no claim.

This is the single lesson every era re-taught in a new costume. In the editor era it was "agents without tests are dangerous." In the process era it was independent review and stop hooks. By 2026 it hardened into proof scenarios and the four words above — and it applies to this guide itself: the stamps exist because the guide obeys its own rule.

The little robot will always project the thumbs-up. Take the receipt instead.

disposable implementation // durable human contract