Session Handoff
Benchmarked against: Anthropic โ Context editing Source: Agent Intelligence Protocol ยง5b Decision: Cloud UB ub-7c698cb60299
Session Handoff ensures unfinished work survives across sessions. When a session ends โ whether intentionally or due to context limits โ the agent's todo list persists to Cloud UB and is automatically restored in the next session.
How it worksโ
At session end (Pre-Exit)โ
1. Agent detects session ending
2. Unfinished TaskList items โ ingest_fragment() to Cloud UB
3. Title: "Session Handoff โ {agent_identity} โ {date}"
4. Tags: session-handoff
At next session start (SessionStart hook)โ
1. Hook auto-queries Cloud UB for session-handoff entries
2. Matching entries โ injected into agent context
3. Agent rebuilds TaskList from handoff data
4. Work continues where it left off
Why not mailbox?โ
Captain explicitly decided against using agent mailbox for handoffs โ messages get missed too easily. Cloud UB with structured tags is more reliable and searchable.
Formatโ
The handoff entry contains:
| Field | Content |
|---|---|
| Title | Session Handoff โ Mac CLI ๅฐๅ
โ 2026-03-05 |
| Tags | session-handoff, [ship] |
| Content | Unfinished todos with status, current context, next steps |
Display formatโ
Todo items use CLI-style indicators:
โ Completed task
โก Pending task
โถ In-progress task
What gets handed offโ
| Included | Not included |
|---|---|
| Unfinished todo items | Completed items |
| Current task context | Full conversation history |
| Blockers and next steps | Temporary debug state |
| Key decisions made this session | Routine operations |