handoff

# Session Handoff Two-mode skill: **Save** state at end of session, **Resume** state at start of next session. ## Product-aware runner and state Claude uses the installed runner and state under `~/.claude`: ```bash HANDOFF_RUNNER="$HOME/.claude/src/scripts/handoff.ts" CC_STATE_ROOT="$HOME/.claude" ``` Standalone Codex uses `${CODEX_HOME:-$HOME/.codex}/darkroom/source/src/scripts/handoff.ts`, but the plugin's stable handoff state is exposed only to hooks as `$PLUGIN_DATA`. In a Codex plugin hook, set `HANDOFF_RUNNER` to that runner and `CC_STATE_ROOT="$PLUGIN_DATA"`. Outside that environment, do not guess a cache path or write into `~/.claude`: manual Codex create/resume/list/clean is unavailable until the host exposes the same plugin-data path to the session. ## Mode: Save Save current session state for later resumption. This is the **end-of-session boundary** skill — for mid-task rollback points before risky operations, use `/checkpoint`. ### Usage ```bash CC_SETTINGS_HOME="$CC_STATE_ROOT" bun "$HANDOFF_RUNNER" create ``` Or use the native command: ``` /handoff ``` ### What Gets Saved Every handoff — auto or manual — always captures real, git-derived data at creation time: - **Project**: name, path, current branch - **Pending changes**: `git status --porcelain` (first 20 lines) - **Key files**: uncommitted paths **union** the files the session ledger observed being changed (see below) - **Recent commits**: subjects of the last 3 commits - **Source**: `manual` o...