codex-transfer

# Codex Session Transfer One-way handoff. Unlike every other codex-advisor skill, there is **no double-check phase** — once the transfer completes, work continues in Codex outside Claude Code, so there is nothing left here to classify. The wrapper's job is whitelisting, error taxonomy, and disable-parity — not verification. ## Phase 1: Analyze **Whitelist for this skill:** `--source <path>`, `--json`. Nothing else — transfer has no prompt, so there is no focus text or model/effort to route. - `--source <path>` — explicit Claude session `.jsonl` to import. Optional; when omitted the companion falls back to the `CODEX_COMPANION_TRANSCRIPT_PATH` env var, which codex-advisor's own SessionStart hook (`hooks/session-start.mjs`) sets automatically — whether or not the Official plugin itself is enabled. - `--json` — when the user passes this, show them the raw JSON payload in Phase 3 instead of the friendly summary. This is independent of the `--json` codex-advisor always adds internally to the companion call (see Phase 2) — that one is for our own parsing, not the user's request. - **Unrecognized token** (any other flag, or free-standing text) → `AskUserQuestion`. Transfer has no positional argument — the companion silently discards anything it doesn't recognize as `--source`/`--cwd`/`--json` (`handleTransfer` destructures only `options`, never `positionals`), so passing it through would do nothing rather than corrupt a prompt. Still don't forward it: ask what the user meant. If...