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

How to resume an interrupted Claude or Codex coding task with Threadport

Find a stopped session in the local workbench, review its evidence, and prepare a continuation command.

Credentials. Session logs can contain secrets; ThreadPort's redaction is heuristic, so review the continuation text and any exported artifacts before sharing them.

Who it is forA 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 problemCoding 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 outcomeYou get a reviewed task with observed files, commands, tests, and an objective you confirmed, plus a continuation text you read before running anything.

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 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 for your agent

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 <project-directory> 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.

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