Switch agents. Keep the thread.

ThreadPort keeps your task in the project: decisions, open tasks, test results and Git state. When you move from Claude Code to Codex, the next agent starts where the last one stopped.

Install the CLI (Node.js 24+)

npm install -g threadport

CLI available on npm v0.5.0
VS Code extension on the Marketplace

~/apiclaude

$ threadport run claude
→ Launching Claude Code with active session context.
$ threadport decision "Keep token IDs in Redis" \
    -r "Shared revocation across instances"
✓ Decision recorded.
$ threadport check npm test
✗ refresh.spec.ts  2 of 14 failed

~/apicodex

$ threadport switch codex
→ Launching Codex CLI with active session context.
## Session [session:9befafd8]
Objective: Fix token rotation
## Open tasks [work-records]
- [open] Write a concurrency test
## Tests [work-records]
- [failed] refresh.spec.ts: 2 of 14 failed

What the next agent receives

A context pack is plain Markdown built from what the session recorded. Every section names its source, and a token budget keeps it short enough to read. Pick a detail level to see the real output for the same session.

Objective, open tasks and current errors first
Live Git branch, HEAD and changed files
Decisions with their reasons, test results and notes
The diff itself in deep and full modes

Loading the context pack…

threadport context --mode standard --explain

A handoff in four commands

Run these from the root of the project you want to track. Everything is stored in .threadport/ next to your code.

Start tracking the project
```
threadport init
```

Describe the task

threadport new "Fix token rotation"
threadport task add "Write a concurrency test"

Work with the first agent

threadport run claude
threadport check npm test

Hand off to the next one
```
threadport switch codex
```

Prefer it automatic? threadport hook install claude gives the agent the context when it starts and records edited files and a summary when it stops.

It stays on your machine

Sessions live in a local SQLite database inside the project, ignored by Git. Nothing is sent anywhere unless an agent you launch sends it under its own rules.

Secrets are redacted: API keys, GitHub and cloud tokens, JWTs and passwords are replaced before storage and before any handoff.
Paths can be excluded: .env, keys and secrets/** are left out by default. Add your own in .threadportignore.
You can audit before sharing: threadport privacy audit counts what would be redacted or excluded, without printing it.

A note as you type it, and as it is stored

$ threadport note "Staging uses token=ghp_R8x2kq7Lm4Pz9Vw1Yb"

- [info] Staging uses token=[REDACTED]

Works with the agents you already use

Supported agents and how ThreadPort connects to them
Agent	How it connects
Claude Code	Interactive or structured runs, native session resume, optional lifecycle hooks
Codex CLI	Interactive or structured runs, native session resume, optional lifecycle hooks
Any CLI agent	A small JSON manifest, run only after you trust it with `threadport plugin trust`
MCP clients	`threadport mcp` exposes the context, handoff and session tools over stdio

Available on the Visual Studio Marketplace

The same thread, inside VS Code

The extension opens each session as a Markdown document you edit in place. Write the next instruction, press Ctrl + Enter, and ThreadPort starts the agent in a terminal with the current context.

Install from the Marketplace

code --install-extension aristideghost.threadport-vscode

Sessions, tasks and decisions in the Activity Bar, with checkboxes for tasks
Switch between Claude Code and Codex from the session document
Add a file or a selected range to the context from the editor
Chat with @threadport and share the session with Copilot through MCP
Changes made with the CLI appear right away
English and French interface

Try it on your next task