Hand a change to another agent

An agent finishes a session, or runs out of context, or you want a person to take over. The next worker needs what the last one knew, and scrolling a diff is a poor substitute.

tovio agent resume <chg-id>

tovio agent resume task:<task-id>

What it assembles

• The originating prompt and run record behind the change, labelled by attestation class.
• The attested rationale, where you are a recipient and can read it.
• The paths the change touched.
• The repository conventions matching those paths.
• Any active peer intent declarations overlapping them — so the next worker knows who else is in there.

The label is the point

A resumed run record says which tier it came from. An observed record is marked UNATTESTED: it was scraped from a runtime transcript, not produced under a capability token, and the fact that it sits next to a real change does not make its contents proven. Read it as context, not as evidence.

It grants nothing

agent resume is read-only and advisory by design, and it must never be consulted in an authorization decision. It hands over knowledge, not authority — the next agent still needs its own token, and that token is still enforced exactly as before. A sealed record the caller cannot open renders as a locked marker; it never leaks plaintext to widen a handover.

The handover, end to end

tovio agent resume <chg-id> --json

tovio agent new successor --model <id> --task "continue <chg-id>" --expires-in 4

tovio agent revoke <old-token-id>

Brief the successor from the resume output, issue it its own scoped token, and revoke the predecessor's. Reusing the old token is the tempting shortcut and the wrong one: provenance would then attribute two agents' work to one token, and you lose the ability to tell them apart later.

It works for people too

Nothing about agent resume is agent-specific on the reading side. It is a good first command when you inherit an unfamiliar change, whoever wrote it.