Continue in a new session

Use ordinary working memory when both sessions share a project and profile. Use a signed handoff file when you want to move a specific checkpoint explicitly.

On this page

Switch from Claude Code to Codex

  1. Connect both tools to the same project and profile. For a new setup, choose both in crosshead quickstart. For an existing project-scoped setup, add the second host with crosshead workspace add.
  2. Let the outgoing turn finish. Check crosshead memory hot --scope all for the finding you want to carry over.
  3. Open the other tool from the same repository. Confirm the profile in its attachment message. Ask it to restate where the work stands and inspect the current Git diff before continuing.

Use Git or your normal file transfer to carry any uncommitted edits across machines. Crosshead carries the working context. For the existing conversation within one tool, use that tool’s native resume.

Pick up recent work on another machine

For automatic hot sync, use the same identity, profile name, and service on both machines. Matching Git remotes normally resolve to the same workspace. If there’s no matching remote, link each checkout with the same workspace label before capturing. crosshead memory sync can help you see whether the source has pending uploads.

crosshead workspace link --name csv-import --workspace-root "$PWD"
crosshead memory sync

Keep the private key in each machine’s local secret store. The service cannot give it back to you. If you only need to carry a single task, use a signed handoff file and leave the identities separate.

Export and import a signed handoff

Find the source session ID in the host’s session information or in the relevant checkpoint in crosshead memory hot --scope all --json. Run the export in the source project. Replace YOUR_SESSION_ID with that ID and choose a new output filename in a private directory.

crosshead handoff export --source claude-code --target codex \
  --workspace-root "$PWD" --session-id YOUR_SESSION_ID \
  --prompt "Continue the CSV import regression test" \
  --output "$HOME/csv-import-handoff.json"

Inspect the file with crosshead handoff explain --file <path> before sharing it. A capsule can include project text and recent findings. The signature identifies the sender and lets the CLI detect changes to the file. Transfer the file privately.

At the destination, run the import from the project you want the handoff to reach. The example assumes the file is in your home folder there too.

crosshead handoff import --target codex --file "$HOME/csv-import-handoff.json"

The receiving profile accepts its own signer. For another identity, verify the signer’s public npub independently, then add --allow-signer <npub>. Capsules older than 30 days are rejected by default. Open a fresh destination session and verify the imported checkpoint against the current files before acting.