Pass the baton between AI coding agents - hit a limit in Claude Code, resume exactly where you left off in Codex, Gemini, or Cursor.
Project description
tapout
Your coding agent tapped out? Tag in the next one.
Hit your Claude Code limit mid-task — tap codex and it picks up exactly where you left off. Same task, same plan, same progress. No re-explaining.
Install
pip install tapout
Installs two equivalent console commands, tap and tapout. Python 3.10+.
How it works
tap out— prints a summarization prompt (also copied to your clipboard). Paste it into your current agent; it replies with a task-state JSON block.tap out --from <file>— ingests that reply and writes two artifacts:HANDOFF.md(human/agent readable) and.tapout/task-state.json(schema, git-friendly).tap <agent>— opens the target agent in the repo, seeded with the handoff. Works forclaude,codex,gemini,cursor, and any agent you add yourself.
Run tap scan to see which agents are installed on this machine.
Zero-effort capture (Claude Code plugin)
Install the bundled Claude Code plugin so capture happens automatically — no manual tap out:
git clone https://github.com/MIthunvasanth/tapout.git
cd tapout
claude plugin marketplace add ./
claude plugin install tapout@tapout
- PreCompact + SessionEnd hooks refresh
HANDOFF.md+.tapout/task-state.jsonautomatically before Claude compacts context or the session ends. After you/exit, the handoff is already written — justtap codex. /tapout:pausecaptures on demand mid-session.tap watchshows a live usage line and printsrun: tap codexwhen your 5-hour window is spent. Add the statusline to~/.claude/settings.json:{ "statusLine": { "type": "command", "command": "tap statusline", "refreshInterval": 5 } }
tap statuslineprintstap: N%and records state thattap watchreads.
Manual capture (CI / scripting fallback)
If you're not using the plugin, capture from a Claude Code session directly. With no --session-transcript, tapout auto-picks the newest session transcript for the current repo:
python -m tapout capture --agent claude # auto-picks this repo's latest session
tap codex # or tap cursor, tap gemini
Pass --session-transcript <path> to pick a specific transcript. This is the same capture logic the hooks invoke.
Zero-install via uvx
Once published, the hooks (and you) can run tapout without installing it: uvx tapout <command>. The plugin's hook launcher prefers your installed package and falls back to uvx tapout.
Adding your own agent
Agents are data, not code. Drop a ~/.tapout/agents.toml to add or override any agent — no package changes:
[mytool]
display_name = "My Tool"
binaries = ["mytool"]
config_dirs = ["~/.mytool"]
resume_style = "cli_prompt" # or clipboard_gui / clipboard_only
launch_template = ["{binary}", "{prompt}"] # {binary} {prompt} {cwd} substituted
version_probe = { args = ["--version"], timeout_sec = 5 }
Then tap resume mytool (or tap scan to confirm it's detected). User keys win over the bundled registry.
Each entry can also set prompt_delivery: "argv" (default), "stdin" (pipe the prompt to the child — bypasses cmd.exe, the safe default for codex/gemini/claude), "file:<flag>" (write the prompt to a file, pass the path via <flag>), or "clipboard".
Note: Gemini CLI's free tier was deprecated in December 2025 — the registry flags this, and
tap scansurfaces the note.
First run in a new folder
The first tap <agent> in a repo may hit the receiving agent's own setup: trust/workspace-approval dialogs, IDE-connect prompts, or a sign-in. That's the target agent, not tapout. Get through those once — subsequent handoffs into that folder go straight to work.
Windows notes
- npm-installed agents ship both an extensionless shim and a real
.cmd; tapout resolves the.cmd(PATHEXT-aware) so launches don't fail with WinError 193. - When an argv-delivery launcher is a
.cmd/.batand the handoff contains shell metacharacters (& | % " ^ < >), tapout will not pass the prompt as a command-line argument (cmd.exe would re-parse it — the "BatBadBut" class of bug). It falls back to clipboard. Agents usingstdinorfiledelivery (codex, gemini, claude) avoid this entirely. - PowerShell's
typemay mangle UTF-8; runchcp 65001first, or openHANDOFF.mdin an editor.
Early alpha (0.1.0.dev0). Manual + auto (Claude Code plugin) handoff; usage monitor via tap watch.
Project details
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file tapout-0.1.1.tar.gz.
File metadata
- Download URL: tapout-0.1.1.tar.gz
- Upload date:
- Size: 33.8 kB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.12
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
3b39bd9a8e252f6234ba3d5abd5164f817c49e52b7f759e7dd8ad34910fa1f74
|
|
| MD5 |
8988761f0316a818b31b248aabf33de2
|
|
| BLAKE2b-256 |
9041b8a659349974904efce8cdab569098778286e03494e6e569ca662b157561
|
Provenance
The following attestation bundles were made for tapout-0.1.1.tar.gz:
Publisher:
release.yml on MIthunvasanth/tapout
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
tapout-0.1.1.tar.gz -
Subject digest:
3b39bd9a8e252f6234ba3d5abd5164f817c49e52b7f759e7dd8ad34910fa1f74 - Sigstore transparency entry: 2082207493
- Sigstore integration time:
-
Permalink:
MIthunvasanth/tapout@243a7b4cfdd00f84ac301e5c823e8b3e02ed7683 -
Branch / Tag:
refs/tags/v0.1.1 - Owner: https://github.com/MIthunvasanth
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
release.yml@243a7b4cfdd00f84ac301e5c823e8b3e02ed7683 -
Trigger Event:
release
-
Statement type:
File details
Details for the file tapout-0.1.1-py3-none-any.whl.
File metadata
- Download URL: tapout-0.1.1-py3-none-any.whl
- Upload date:
- Size: 26.8 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.12
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
6e1790f1600229b849cf525bf74be69bb9344b96b9ba4c8749c05e2b0bce983f
|
|
| MD5 |
cff7f4108384e0115d28ed24cf9bda77
|
|
| BLAKE2b-256 |
ef23f0b0f0d94a83dafa715c433137601d484e4cc3be28bed68c20b506702526
|
Provenance
The following attestation bundles were made for tapout-0.1.1-py3-none-any.whl:
Publisher:
release.yml on MIthunvasanth/tapout
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
tapout-0.1.1-py3-none-any.whl -
Subject digest:
6e1790f1600229b849cf525bf74be69bb9344b96b9ba4c8749c05e2b0bce983f - Sigstore transparency entry: 2082207499
- Sigstore integration time:
-
Permalink:
MIthunvasanth/tapout@243a7b4cfdd00f84ac301e5c823e8b3e02ed7683 -
Branch / Tag:
refs/tags/v0.1.1 - Owner: https://github.com/MIthunvasanth
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
release.yml@243a7b4cfdd00f84ac301e5c823e8b3e02ed7683 -
Trigger Event:
release
-
Statement type: