← Blog
Week of

Retrospective reconstruction · Published · Weekly archive

Leave a checkpoint someone can open

Long-running work needs saved results between the start and the final report.

Field NotesRetrospective

Retrospective field note for 2026-07-27, reconstructed on 16 November 2026. The archive date is not a claim of publication at the time.

A progress bar at 70% means little if there is nothing to open.

A complete first draft means something. So does a tested component, a source list with dates or a saved export. Use those as checkpoints. If the process stops, the next worker should inherit less work, not just a claim that a lot happened.

Leave a short handoff beside the files. Which source is current? Which approach was rejected? What failed? Has anything already been sent or changed outside the workspace? Those details prevent repeated investigation and duplicate actions.

A long task also has to remain steerable. If the person narrows the brief, stop work on the discarded part and tell any active workers. Continuing the original plan for another hour is not autonomy worth having.

Opus 5 belongs in longer-task evaluations, but duration alone proves nothing. Inspect the checkpoints and the assembled result. The task should become more recoverable as it progresses, even if the current session disappears.

Anthropic introduced Claude Opus 5 on 24 July. Source.

All posts Work with me