# Looking complete isn’t being complete

Introducing Handover

The next agent only knows what your note says.

_Gaps caught before the next agent inherits them._

```
handoff: guest-checkout
true_at_sha: a1b2c3d4e5f6
first_action: Run the pending migration on the preview database
status: done
```

87/100, header invalid

_A Handover is never done on belief, only on a passing check._

```
verify_cmd: npm test -- guest-checkout && npm run typecheck
```

100/100, header valid

[Read the code](https://github.com/geekidharsh/handover)

1. **Write**: Write a handoff from live git state.
2. **Score**: It scores the note against a strict format.
3. **Pick up**: The next agent picks up what is actually there.

**Why we built it**

An agent’s handoff note can look complete and still leave out what matters. The next agent inherits the gap and acts on it. Handover holds a note to a strict format: the commit its claims were true at, the one first action, and the command that proves the state. A note that says done must show how.

**The result so far**

- A Handover note: Score 100/100; Traps covered 9 of 9; Valid yes
- A session summary: Score 8 to 16/100; Traps covered 0 of 9; Valid -

Three scenarios, three planted traps in each.

**The paper**

Paper · August 2, 2026

[Handover: An Enforced Agent-to-Agent Handoff Document and a Trap-Based Benchmark for Measuring Context Transfer](https://geekidharsh.github.io/handover/paper/handover.pdf)

> “A cold agent given only the artifact and repository access should reach the same decisions the sender would.”

Read the paper: https://geekidharsh.github.io/handover/paper/handover.pdf

**Install in Claude Code**

```
/plugin marketplace add geekidharsh/handover
/plugin install handover@handover
```

_Two commands, then restart._

On GitHub: https://github.com/geekidharsh/handover
Read the spec: https://github.com/geekidharsh/handover/blob/main/PROTOCOL.md

## For agents

Install as a Claude Code plugin, restart, then `/handover:write` at every session boundary. Never mark `status: done` without a `verify_cmd`; the plugin's write gate will block it anyway.

- [llms.txt](https://www.household.dev/llms.txt)
- [tools/index.json](https://www.household.dev/tools/index.json)
