# Long-running agents: write a useful session handoff

A useful handoff records the objective, completed work, verification results, open issues and the next concrete action. Keep pointers to real files and relevant versions. The next session should check the current workspace before relying on the summary.

## Worked example

“Almost finished” is not actionable. “Parser updated; regression check A passed; case B still fails; inspect src/parser.ts next” gives the next session a starting point. This is an illustrative handoff, not a claim about a deployed agent.

## Copyable prompt

```text
Write a handoff for [WORK SESSION]. Include objective, current file/version pointers, completed changes, checks actually run and their results, unresolved failures, constraints and the next concrete action. Separate verified facts from assumptions. Do not mark work complete because a summary was written. Tell the next session which current state it must inspect before continuing.
```

## Checklist

- Link to actual artifacts and versions.
- Record checks with observed results.
- Keep unresolved failures explicit.
- Start the next session by verifying current state.

## Further reading

[Anthropic: long-running agent harnesses](https://www.anthropic.com/engineering/effective-harnesses-for-long-running-agents)