Short answer: you don't have to log out. Claude Code keeps its settings and history in one config folder, ~/.claude by default, and the CLAUDE_CONFIG_DIR variable points it at another one. Give each account its own folder and both stay signed in, side by side. crewrota is a free, open source CLI that sets this up for you and adds your setup, shared history and a usage view on top.
I'm a software engineer. During the day I use Claude Code for my job, and in the evenings and at weekends I use it for my own projects. Those are two different Claude logins, and for a while that was more annoying than it should have been.
The problem: one login at a time
By default, Claude Code runs as one login at a time on a machine. Switching from my work login to my own meant this:
- Run
/logout. - Sign in again with the other account in the browser.
- Find the folder and the session I was in, and get my head back into the task.
None of these steps is hard. But when you switch often, it adds up, and you lose your train of thought every time.
There was a second problem. Each login keeps its own history, so --resume on one account could not find a session I had started on the other. The work was split in two places.
How to switch Claude Code accounts without logging out
Claude Code reads an environment variable called CLAUDE_CONFIG_DIR. The Claude Code docs describe it like this:
"Override the configuration directory (default:
~/.claude). All settings, session history, and plugins are stored under this path."
The same page calls it "useful for running multiple accounts side by side". Give each login its own folder, and each one stays signed in. Two terminals, two accounts, at the same time.
You can do it by hand:
CLAUDE_CONFIG_DIR=~/.claude-work claude
CLAUDE_CONFIG_DIR=~/.claude-personal claude
That works, and it is what crewrota is built on. But by hand you lose three things:
-
Your setup. Your skills, agents, commands, plugins, settings and
CLAUDE.mdlive in~/.claude. A new folder starts empty. - Your history. Each folder keeps its own sessions, so they are still split.
- The overview. Nothing tells you which login has usage left before you start.
What crewrota adds
crewrota is a small command-line tool around that variable. Each login is a crew member, with its own folder.
-
crew add workcreates a member and opens Claude Code's own login for it. -
crewopens a menu. Pick a member, its model and effort, and Claude Code starts as that login. Your main~/.claudelogin is never touched. - Your skills, agents, commands, plugins, settings and
CLAUDE.mdfrom~/.claudereach every member. crewrota only reads them. - Members on the same ship share history, so
--resumein one member finds a session started in another. -
crew quotashows every member's 5-hour and weekly usage on one screen, andcrew widgetputs the same bars on your desktop.
To try it:
npm install -g crewrota
crew add work
crew add personal
crew
You need Node 22.19 or newer and Claude Code. Windows is the main platform, and macOS is in beta.
Your accounts and Anthropic's terms
crewrota is for one person using their own Claude subscriptions. Each member logs in through Claude Code's own login, and crewrota never reads, copies or moves credentials. It runs the real claude program; nothing goes through a proxy.
Read Anthropic's Consumer Terms and Usage Policy for your plan before you use more than one account.
Questions about crewrota
Can I use two Claude Code accounts at the same time?
Yes. Give each account its own config folder with CLAUDE_CONFIG_DIR and start each one in its own terminal. Claude Code's docs call the variable useful for running multiple accounts side by side.
Does crewrota change my main Claude Code login?
No. It only reads your main ~/.claude folder, to share your setup with each member. Your main login is never touched.
Where do the logins live?
Each one sits in that member's own folder, put there by Claude Code's own login. crewrota never reads or copies them, and crew backup leaves them out.
Is crewrota free?
Yes. crewrota is open source under the MIT license, on npm and GitHub. Windows is the main platform, and macOS is in beta.
It's the setup I use every day. If you try it, I'd like to hear what breaks: open an issue on GitHub.

Top comments (0)