Resume any agent session without starting from zero.

Companion Handoff is the continuity bridge for Codex, Claude Code, Kimi, and Grok. It turns overwhelm into 6 session modes, 4 agent routes, 8 handoff prompts, 7 continuity checks, 7 proof gates, and 12 import captures.

Simple layer. When a new session starts, read companion-handoff.md before explaining everything again. Pick one mode, one unit, one done-when, and one proof gate before opening another agent, project, course, or tab.

The operator command calls work/life-os-companion-handoff.mjs. It writes companion-handoff.md, companion-handoff.json, and companion-handoff-import.json. The file is local-only and manual-only, and it is a continuity guide, not an autonomous agent runner.

Run the handoff

node work/life-os.mjs companion

# or directly:
node work/life-os-companion-handoff.mjs

# then open:
outputs/life-os-command-center/companion-handoff.md

Choose a route

6 session modesLost, today, revenue, project, agent, and learning.

4 agent routesCodex, Claude Code, Kimi, and Grok each get a use case and proof expectation.

8 handoff promptsStart-session, execute-one, validator, sales, project, presence, learning, and closeout.

7 continuity checksRead progress, read today, choose one unit, define proof, protect privacy, keep manual boundaries, and close the journal.

7 proof gatesEvery session needs a real command, file, result, or reproducible blocker.

12 import capturesLoad the handoff queue into the cockpit when you need visible continuity.

Current proof counts: 6 session modes, 4 agent routes, 8 handoff prompts, 7 continuity checks, 7 proof gates, 12 import captures, local-only.

Import into the cockpit

companion-handoff-import.json adds a local queue for opening the handoff, choosing a mode, using Codex, Claude Code, Kimi, or Grok with a bounded unit, validating the proof gate, and closing the session.

Guardrails

This is not autonomous Jarvis. It does not send messages, publish posts, scrape the web, touch Gmail/OAuth, automate payments, schedule calendars, execute agents automatically, or publish private command-center state.