
carry
io.github.vamzzismePublished by GitHub account vamzzismev0.4.4Updated Nov 7, 2026
Share Claude Code and Codex chats or projects with friends through your own Google Drive.
Overview
Lets an assistant share Claude Code and Codex chats or whole projects with friends through the user's own Google Drive, and pick up shared sessions.
- What you can do
- Share chats and projects: send a named chat or a whole repo bundle (chats, memory notes, handoff) to a paired friend or by email/link
- Manage the inbox: list what friends sent, open a received chat into Claude Code, Codex or a chat app, and send borrowed work back
- Pair and track: add friends by email or pairing code, list paired friends, and see what has been shared
- Rename and sync chats, share a written summary, and check setup and versions
- When to use it
- Useful when you want to hand a coding session or project to another account, another tool or a friend's machine with full history, or when you want to ask an assistant in plain language to share a chat or check your carry inbox instead of using the terminal.
- Requirements
- Runs locally over stdio via the npm package @heyvamz/carry (Node 22.15 or newer; macOS, Windows or Linux). Needs a Google sign-in through carry setup to use the user's own Google Drive, plus network access to Google Drive, npm and GitHub. Desktop apps only.
Installation
In SourceWeft
- Open carry in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
carry
AirDrop for AI chats and projects. Serverless: it travels through your own Google Drive, nothing is hosted by us. Out of tokens? Keep coding.
carry moves a Claude Code or Codex session, with its full history, to another account, another tool or a friend's laptop. Or hand over a whole project, memory and all, so the next agent knows what was tried and why.
Shared chats go into your own Google Drive. There is no carry server and no account with us.
Website · GitHub · built by @heyvamz · A VXMZ product
Why not just paste a summary?
A summary keeps what the AI chose to remember. carry keeps every message, command, error and dead end, and the next agent resumes it as its own session, so it doesn't retry the fix that already failed.
Install
Needs Node 22.15 or newer. Works on macOS, Windows and Linux.
On Linux you may need sudo npm install -g @heyvamz/carry.
Already use Google Drive for desktop, Dropbox or iCloud? Run carry setup (or carry setup ~/Dropbox/carry) instead and
share that one folder with your group.
Use it
Inside Claude Code or Codex, type /carry and it walks you through everything. Or from a terminal.
With friends: pair once, then just pick from your inbox
Then:
If you also kept working on your copy meanwhile, carry opens Riya's version next to yours and overwrites nothing.
Add --auto-return when sharing to have her carry send it back on its own (run carry install-hook for Claude Code).
Everything Riya's carry reads is encrypted with a key that only lives in your pairing codes.
Without pairing
Share a whole project
It bundles the newest chats (and any you add), Claude Code's memory notes, CLAUDE.md / AGENTS.md and a handoff. The code
itself goes through git. Riya clones the repo, then carry open <number> --to claude_code --dir ./my-app, and later
carry return --project my-app brings back her chats and any memory notes Claude picked up.
Claude Code gets your memory notes and a handoff note where it reads them at the start of a session; Codex gets a
.carry/ folder and a pointer in AGENTS.md. Nothing of theirs is overwritten.
Chat apps
claude.ai, ChatGPT and the Claude app keep chats on their servers, so carry shares a written summary there:
carry open <link> --to chat copies a prompt and shows the handoff.md to attach.
No terminal? Ask your AI
carry also runs as an MCP connector. Add it once, then just say "share this chat with Riya", "what's in my carry inbox?" or "send it back to Riya".
Claude Desktop, one click: download carry.mcpb and double-click it.
Claude Code plugin (connector + /carry skill together):
Claude Desktop by hand (Settings, Developer, Edit Config) and Cursor (~/.cursor/mcp.json):
Codex (~/.codex/config.toml):
On Windows, use "command": "cmd" and put "/c", "npx" at the start of the args. Restart the app after saving.
Commands
Privacy
- carry runs on your computer. Chats go from your computer to your Google Drive and nowhere else.
- It asks Google for the narrowest Drive permission: it can only see files it created.
- API keys, tokens, private keys and
KEY=valuelines are replaced with[REDACTED]before anything leaves your laptop. This is pattern based, so don't share chats full of secrets you care about. - Nothing is shared unless you pick it.
- We collect nothing. carry has no server and no telemetry; the only network calls are to Google Drive (your account), npm (update check) and GitHub (downloading txcript once).
- Shared files stay in your Drive until you delete them there. Local settings live in
~/.carry/until you delete that folder. - Who sees a shared chat is up to you: paired friends, the emails you name, or anyone with the link if you choose
--link. - Contact: [email protected]
Full policy: carry-si.vercel.app/privacy
Notes
- Google may show "Google hasn't verified this app" while carry is in Google's testing stage. Click Advanced, then continue.
- Stop the daily update check with
CARRY_NO_UPDATE_CHECK=1. - Something not working? See Troubleshooting.
Built on txcript by SkillSync, which converts chats between tools. Apache-2.0 license.
Source: README.md at commit 8fc788f
Tools
0Version history
1- v0.4.4LatestNov 7, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
