DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to hand off a Claude session to Codex through the CLI with Threadport

Extract a Capsule from a Claude session file and write a Codex handoff file with the handoff command.

Credentials. The extracted Capsule may contain code excerpts and paths from the session; the README says to inspect artifacts before sharing them.

Who it is forA developer or automation script that needs a validated, file-based handoff from a Claude session to Codex without opening the workbench.

The problemMoving a task between agents usually means copying chat text by hand, which loses the observed state and invites mistakes.

The outcomeYou get a Capsule JSON file, a validated Codex handoff JSON file, and a clear confirmation that both files passed validation.

What you need first

  • Node.js 24 or newer (the README requires Node >=24.0.0 for this checkout)
  • A local clone of Frankie-Xu/threadport with npm available
  • Local Claude or Codex session logs, or a Cursor Copy Transcript export saved as UTF-8 text
  • The target Agent (Claude or Codex) installed locally if you want to launch a continuation

Steps

  1. Run npm ci in the Threadport checkout.
  2. Run npm run build.
  3. Run node dist/src/cli.js extract --from claude --session ./session.jsonl --project . and note the output path it prints.
  4. Run node dist/src/cli.js validate /path/printed/by/extract.json.
  5. Run node dist/src/cli.js handoff --to codex /path/to/capsule.json --format json --out ./handoff.json, then run node dist/src/cli.js validate --handoff ./handoff.json.

Prompt for your agent

Using the Frankie-Xu/threadport repo after `npm ci` and `npm run build`, extract a Capsule from <session-file> with --from claude and --project <project-directory>, then create a Codex handoff at <handoff-path>. Report both printed output paths and confirm that `node dist/src/cli.js validate --handoff <handoff-path>` succeeds.

Caveat. The CLI validates before writing and does not run next_action, but the README warns that secret scanning is heuristic and does not guarantee removal of all credentials.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page