appreciate you building this! I have two Claude max accounts. The way I do it is that I have two app launchers (claude desktop). I use the desktop app and a different data directory for each launcher like `open -n -a /Applications/Claude.app --args --user-data-dir="<its profile directory>"`. I got my first Claude to make me two different launchers for the two apps, and it's been working perfectly. wdyt?
The only problem I've noticed is with Claude in Chrome. It seems to not work well in the second account. And this makes sense because it was designed just for one app. Do you find yourself having the same problem with this setup? have you tried the second one with the Claude in Chrome ext?
This is great. My enhancement was to create a .claude-profile file which specifies the account alias. "claude" can be aliased to read the file, set the correct env var, and launch claude.
Another benefit was if no .claude-profile file exists, claude refuses to launch.
Do you expect vibe-coded slop to care about such things? Also, there's already another app, https://github.com/realiti4/claude-swap, which is also vibe-coded, but it's maintained and tested.
If it's honestly 'One account is paid for by my employer and used as a tool for my job' and 'One account is for personal use, where I work on passion-projects and the likes' I think it's fine....? Not a lawyer but I'd assume as long as you're not using it to bypass usage limits Anthropic wouldn't even really notice or care.
I use the Claude Code desktop app for work, and the CLI for personal, so I'm always logged into both accounts!
appreciate you building this! I have two Claude max accounts. The way I do it is that I have two app launchers (claude desktop). I use the desktop app and a different data directory for each launcher like `open -n -a /Applications/Claude.app --args --user-data-dir="<its profile directory>"`. I got my first Claude to make me two different launchers for the two apps, and it's been working perfectly. wdyt?
The only problem I've noticed is with Claude in Chrome. It seems to not work well in the second account. And this makes sense because it was designed just for one app. Do you find yourself having the same problem with this setup? have you tried the second one with the Claude in Chrome ext?
I use this: https://gist.github.com/KMJ-007/0979814968722051620461ab2aa0...
Simple and works great but requires one alias per account
This is great. My enhancement was to create a .claude-profile file which specifies the account alias. "claude" can be aliased to read the file, set the correct env var, and launch claude.
Another benefit was if no .claude-profile file exists, claude refuses to launch.
simple and easy - thank you
Does it share the global ~/.claude/CLAUDE.md file? For some use case I'd like that, for others it could be problematic.
Do you expect vibe-coded slop to care about such things? Also, there's already another app, https://github.com/realiti4/claude-swap, which is also vibe-coded, but it's maintained and tested.
thanks for sharing this one!
revolutionary. you can do this with 2 lines of shell code.
i do this: https://github.com/acuteaura/universe/blob/main/overlays/cla...
Or use https://omp.sh and add multiple accounts. omp tracks usage and when limit is reached it uses the next account.
Sadly incompatible with Claude subs.
Subs are supported
don't people get banned for doing this kind of thing?
If it's honestly 'One account is paid for by my employer and used as a tool for my job' and 'One account is for personal use, where I work on passion-projects and the likes' I think it's fine....? Not a lawyer but I'd assume as long as you're not using it to bypass usage limits Anthropic wouldn't even really notice or care.
Another way for those who use mise. You can auto-switch accounts by directory:
~/development/account1/mise.toml:
[env]
CLAUDE_CONFIG_DIR = "{{ env.HOME }}/.claude-account1"