# AI use cases for Threadport (Frankie-Xu/threadport) Repo: [Frankie-Xu/threadport](https://github.com/Frankie-Xu/threadport) | Use cases: 3 | Page: https://dedupedai.com/use-cases/frankie-xu-threadport/ ThreadPort is a local tool that finds unfinished AI coding tasks, reviews their observed evidence, and prepares a continuation for Claude or Codex. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Resume an interrupted Claude or Codex coding task: https://dedupedai.com/use-cases/frankie-xu-threadport/resume-interrupted-claude-or-codex-task/ - Hand off a Claude session to Codex through the CLI: https://dedupedai.com/use-cases/frankie-xu-threadport/hand-off-capsule-to-codex-from-cli/ - Import a Cursor transcript as a paused handoff: https://dedupedai.com/use-cases/frankie-xu-threadport/import-cursor-transcript-as-paused-handoff/ ## How to resume an interrupted Claude or Codex coding task with Threadport Repo: [Frankie-Xu/threadport](https://github.com/Frankie-Xu/threadport) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Find a stopped session in the local workbench, review its evidence, and prepare a continuation command. **Who it is for:** A developer whose Claude Code or Codex session stopped mid-task and who wants to restart it in the same project without rebuilding the context by hand. **The problem:** Coding sessions end before the work is done, and the next session starts with no record of what was tried, what changed, and what failed. **The outcome:** You get a reviewed task with observed files, commands, tests, and an objective you confirmed, plus a continuation text you read before running anything. ### Steps 1. Run `npm ci` in the Threadport checkout. 2. Run `npm run build`. 3. Run `node dist/src/cli.js ui --no-open`, open the loopback link printed in the terminal, and add an explicit workspace and source directory in Settings. 4. Refresh the source, find the session in History, and create or attach a task. Review the observed evidence and confirm your objective and constraints. 5. Prepare a continuation, read the complete text, and copy the fixed ThreadPort command to a terminal. Confirm the prompt before the compatible installed Agent launches. ### Prompt to paste into your agent ```text Using the Frankie-Xu/threadport repo built with Node 24, start the local workbench with `node dist/src/cli.js ui --no-open` and attach the session in as a task. Report the observed files, commands, and failures, and confirm that the continuation text contains no unconfirmed objective before any launch. ``` ### Caveat ThreadPort reads only the explicit workspace and source directories you configure and does not execute next_action, but it can only show evidence the session logs actually recorded. Risk, credentials: Session logs can contain secrets; ThreadPort's redaction is heuristic, so review the continuation text and any exported artifacts before sharing them. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/frankie-xu-threadport/resume-interrupted-claude-or-codex-task/ ## How to hand off a Claude session to Codex through the CLI with Threadport Repo: [Frankie-Xu/threadport](https://github.com/Frankie-Xu/threadport) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Extract a Capsule from a Claude session file and write a Codex handoff file with the handoff command. **Who it is for:** A developer or automation script that needs a validated, file-based handoff from a Claude session to Codex without opening the workbench. **The problem:** Moving a task between agents usually means copying chat text by hand, which loses the observed state and invites mistakes. **The outcome:** You get a Capsule JSON file, a validated Codex handoff JSON file, and a clear confirmation that both files passed validation. ### 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 to paste into your agent ```text Using the Frankie-Xu/threadport repo after `npm ci` and `npm run build`, extract a Capsule from with --from claude and --project , then create a Codex handoff at . Report both printed output paths and confirm that `node dist/src/cli.js validate --handoff ` 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. Risk, credentials: The extracted Capsule may contain code excerpts and paths from the session; the README says to inspect artifacts before sharing them. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/frankie-xu-threadport/hand-off-capsule-to-codex-from-cli/ ## How to import a Cursor transcript as a paused handoff with Threadport Repo: [Frankie-Xu/threadport](https://github.com/Frankie-Xu/threadport) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Turn a copied Cursor chat transcript into a paused Capsule that you review before acting. **Who it is for:** A Cursor user who wants to continue a chat in another agent and has only the transcript text available. **The problem:** A Cursor chat transcript has no complete tool results, so it is easy to assume that edits and tests happened when the record does not show them. **The outcome:** You get a Capsule marked paused with visible instructions and unverified assistant context, plus separate current Git state, so you can check the original export before acting. ### Steps 1. Run `npm ci` in the Threadport checkout. 2. Run `npm run build`. 3. In Cursor, use Chat actions, Copy, Copy Transcript, then save the text as UTF-8 plain text with a .txt or .md extension. 4. Run `node dist/src/cli.js extract --from cursor --session /path/to/cursor-transcript.txt --project /path/to/project --out /path/outside/project/capsule.json`. 5. Read the stderr warning and the Capsule constraints, then check the original export before continuing the work. ### Prompt to paste into your agent ```text Using the Frankie-Xu/threadport repo built with Node 24, extract a transcript-only Capsule from with --from cursor and write it to outside the project. Report the status field and confirm that files, commands, tests, failures, completed, and decisions are empty. ``` ### Caveat The README limits this path to a narrowly tested Cursor 3.20.10 transcript on macOS, so other Cursor versions and surfaces are not covered. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/frankie-xu-threadport/import-cursor-transcript-as-paused-handoff/