← Blog
Week of

Retrospective reconstruction · Published · Weekly archive

The handoff should fit on one screen

A transcript can contain everything and still be a terrible place to resume a task.

Field NotesRetrospective

Retrospective field note for 2025-10-06. Reconstructed in November 2026 from dated sources, not originally published on the archive date.

A transcript can contain everything and still be a terrible place to resume a task.

After September’s Sonnet 4.5 and Agent SDK release, I’m interested in the state a long-running workflow leaves behind. Another worker should not need to excavate a conversation just to find the next step.

For a code change, give them the goal, the constraints, the current diff, the failing check and the next thing to test. For research, separate established facts from open questions and keep the sources. For an external action, state whether it was prepared, submitted or confirmed.

Update that record when the state changes. If the tool succeeds but the checkpoint still says “pending”, a restart can repeat something that already happened. That’s particularly unpleasant when the action sends, buys or deletes.

Parallel work needs someone to reconcile the reports. Three individually sensible updates can disagree about the current state. The user shouldn’t be asked to arbitrate because the internal coordination got complicated.

The checkpoint isn’t a diary, and it doesn’t need to preserve every thought. It needs enough information for the next step to be correct. Start there. If it takes longer to read the handoff than to repeat the work, the handoff needs editing.

Sources

All posts Work with me