Introducing carry: keep coding when you run out of tokens
You are two hours into a Claude Code session. The agent finally understands the bug, has tried three fixes, knows which one failed and why. Then you hit your usage limit.
The usual move is to ask for a summary and paste it into another tool or account. It works, badly. A summary keeps what the AI chose to remember and drops what matters most in a long session: the exact errors, the commands that ran, the approaches that already failed. The next agent starts half blind and tries the same broken fix again.
Move the session, not a summary
carry takes the actual session, every message, command and dead end, and moves it to wherever you have tokens left: another Claude account, Codex, or a friend's laptop. It arrives as a real session the next agent resumes as its own. Under the hood it uses txcript, an open converter between AI tools.
Built for groups
The point is to share leftover tokens with the people you build with. Pair with a friend once, then carry share <chat> --to riya drops the chat in her inbox. She opens it on her own account and, when she's done, carry return sends her work back to you. If you both kept going, carry keeps both versions and overwrites nothing.
It works for whole projects too: recent chats, Claude's memory notes and CLAUDE.md travel together, so a fresh session on another laptop knows your decisions.
Your Drive, not our servers
carry has no server and no account. Shares go into your own Google Drive, with the narrowest permission Google offers: carry can only see files it created. API keys and tokens are stripped before anything leaves your laptop, and friend shares are encrypted with a key only your pairing codes hold.
Try it
Paste the setup prompt into Claude Code or Codex, or install it by hand with npm install -g @heyvamz/carry. It is free and open source. If it saves you an afternoon, a coffee keeps the studio going.