Agent Workflows

Handoffs are part of the agent

1 min read

A handoff is part of the agent, not paperwork around it.

When work spans runs, the next session should not have to rediscover state by poking around. The useful handoff is small:

  • last verified file
  • next file
  • current constraints
  • one unfinished issue
  • one concrete verification step

For example:

checked:
  src/routes/billing.ts

next:
  src/routes/invoices.ts

remaining:
  confirm redirect path after login

verify:
  run the migration test after the patch lands

A handoff should also name the stop point. If the run hit a blocked assumption, say so. If a file still needs verification, say so. If a decision is settled and should not be reopened, record that too.

Operator notes are better than polished summaries because they preserve what the next run needs to do. The goal is not to document the whole session. It is to make the next agent useful without rebuilding the previous hour.

Jeremy London

About Jeremy London

Engineering leader and builder in Denver. I write about AI platforms, agents, security, reliability, homelab infrastructure, and the parts of engineering work that have to survive production.