Carrying a thread
constant carry does the same carry as a host switch, but without opening a
hosted terminal. It writes the target runtime's native session and prints the
resume command.
Preview first
--dry-run reads and distills but writes nothing:
constant carry --from codex --to claude --dry-run
constant carry --from codex --to claude --dry-run --debugCarry
constant carry --from codex --to claude
# carried -> claude session 8da587a7
# resume with: claude -r 8da587a7Then resume in the target runtime with the printed command.
Continue vs. new
By default carry continues the current target projection for the conversation.
If codex[1] already has claude[1.1], another carry to Claude updates that
same Claude session. Use --new for a separate continuation:
constant carry --from codex --to claude --new
# codex[1] -> claude[1.2]Target a specific session
Instead of the latest session in the current directory, point at one explicitly:
constant carry --session <path-or-session-id> --to codexMachine-readable output
constant carry --from codex --to claude --jsondistill is kept as an alias for carry, but carry is the public verb.
Next: Sessions & trail.