Write a handoff document summarising the current conversation so a fresh agent can continue the work. Create a unique temporary directory with the platform's secure temp helper (for Node, fs.mkdtempSync(path.join(os.tmpdir(), "handoff-"))) and write handoff.md inside it. Report the absolute path.

If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.

Preserve the actual receiving runtime and resolved role/model configuration under Key context. Do not inject orchestration defaults into an unrelated continuation. Writing a handoff does not launch a worker or change the active model. When continuing a complete run, include its ledger and per-slice result paths under Pointers, and preserve authorization, frozen gates, unresolved rulings, and agent IDs needed to resume. The receiving Codex must verify agent liveness; an ID from a previous session is not proof that a worker is still running.

Document structure

The handoff is read by another agent, so its shape is fixed. Produce exactly these eight sections, in this order, with these headings verbatim. Lead with intent and next steps, not narrative history — a fresh agent should scan top to bottom and start working.