v1.0.0 · free and open source
cchandover runs Claude Code under as many accounts as you have, side by side: personal, work, a client's. Hit a usage limit on one, and it hands the conversation to another in one command.
npm install -g cchandoverClick a command to run it.
Claude Code holds one login at a time. Switching means logging out and back in, and when an account runs out mid-task, the conversation and everything Claude learned about your project stay behind with it.
cchandover gives every account its own login, so they all stay signed in, and moves a conversation to whichever one you need to keep going.
What it does
Each account gets its own folder and login. Logging in or out of one never touches another, and you can run them side by side in different terminals.
cchandover workWhen one account hits its limit, cchandover copies the conversation and that folder's memory to any account you choose, then opens it there so you carry on.
cchandover handoff personal workMemory that already exists on the receiving account is kept. A conversation that was continued on both copies is left alone, and cchandover tells you where to resume it.
cchandover handoff personal work --pickNew accounts share your CLAUDE.md, skills, agents and commands, so your instructions follow you. Settings are copied, so each account can have its own.
cchandover add workHandoff
Handing a conversation to another account means it's processed under that account's organization. cchandover names the organization and asks before it copies. If your workplace doesn't allow moving work between accounts, don't.
Commands
Opens Claude Code logged in as work. Anything after the account name works the same as it does with plain claude.
Run it in the folder you were working in. It finds your latest conversation there on personal, names the organization it's going to and asks first, copies the conversation and memory to work, and opens it there. Any two accounts work: cchandover handoff work client, or back again with cchandover handoff work personal.
Creates ~/.claude-client, shares your CLAUDE.md, skills, agents and commands with it, copies settings.json, then opens the login.
Shows every account with its email, organization and folder.
Forgets the account and keeps its folder and login. With --purge, it also logs the account out and deletes its folder, after asking.
Checks that Claude Code is installed, every account is logged in, and the shared links still work. For anything wrong, it says how to fix it.
Prints a claude-<account> shortcut for each account. Add eval "$(cchandover shell-init)" to your shell profile to use them.
No. Each account keeps its login in its own place, so they all stay signed in and you can run them at the same time in different terminals.
cchandover itself makes no network requests. It copies files on your computer and starts Claude Code, which talks to Anthropic as it always does, under the account you picked.
The latest one from the folder you run it in. Add --pick to choose from a list, or --session <id> for a specific one. Run it from the same folder you started Claude Code in.
As many as you like. Personal and work are only examples: name them after clients, teams or anything else, and hand a conversation between any two.
Yes: cchandover handoff work personal. If you only carried on with one copy, handing it over again brings the older copy up to date.
Claude Code, and Node.js 20.16 or newer (or Bun). It's built and tested on macOS. Linux should work; Windows isn't supported yet.
No. It's an independent open-source project. It uses Claude Code's own commands for logging in and checking accounts, and changes nothing in Claude Code itself.
Something else? Open an issue on GitHub.
Install it, then add your other accounts:
npm install -g cchandovercchandover add work