accounts
Skill448 starsChanged 6 days agoMITView on GitHub
Manage multiple Claude Code accounts: add, list, check, launch, and install shell aliases for 10+ isolated CLAUDE_CONFIG_DIR profiles.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- grechj/Australian-Builders-Braintheir own version, first seen Oct 17, 2026
- harshsinghmp/muse-skillstheir own version, first seen Oct 15, 2026
- notque/claude-code-toolkitword for word, first seen Oct 8, 2026
- qbeka/jev-job-searchtheir own version, first seen Oct 4, 2026
- MGrin/bb-plugin-accountstheir own version, first seen Sep 13, 2026
Other versions5 projects use a version of this.
Word for word · 1
- notque/claude-code-toolkit★ 448100% same
Edited · 0
None found.
Wrote their own version · 4
- qbeka/jev-job-search★ 5same name
- MGrin/bb-plugin-accounts★ 4same name
- harshsinghmp/muse-skills★ 1same name
- grechj/Australian-Builders-Brain★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository64 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- assessmentSkill
- dataSkill
- business-opsSkill
- code-qualitySkill
- comment-qualitySkill
- condenseSkill
- joy-checkSkill
- content-engineSkill
- contentSkill
- headlinesSkill
- image-genSkill
- image-to-videoSkill
- series-plannerSkill
- topic-brainstormerSkill
- video-editingSkill
- writingSkill
- domainSkill
- cli-designSkill
- frontendSkill
- frontend-slidesSkill
- jev-designSkill
- webgl-card-effectsSkill
- game-asset-generatorSkill
- game-devSkill
- game-trailerSkill
- motion-pipelineSkill
- browser-jev-automationSkill
- cve-source-checkSkill
- deploySkill
- endpoint-validatorSkill
- headless-cron-creatorSkill
- kubernetesSkill
- githubSkill
- auto-dreamSkill
- building-with-jevSkill
- codexSkill
- docs-sync-checkerSkill
- doSkill
- dSkill
- grill-jevSkill
- toolkitSkill
- workflow-helpSkill
- debuggingSkill
- plant-seedSkill
- processSkill
- pr-workflowSkill
- quickSkill
- testingSkill
- with-anti-rationalizationSkill
- workflowSkill
- worktree-agentSkill
- programmingSkill
- architecture-deepeningSkill
- codebase-analyzerSkill
- markdown-converterSkill
- news-collectionSkill
- researchSkill
- roastSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 64
Use named aliases (cwork, cpersonal) rather than sequential ones (c1, c2) — named aliases are self-documenting and you won't need list to …
- Very specific: line 74
After add, the script prints a login command.
- Very specific: line 118
Every alias and launch pass DEFAULT_CLAUDE_ARGS from scripts/manage-accounts.py before your own arguments.
- Very specific: line 121
Use --dry-run to preview changes before writing:
- Distinctive: line 129
If you have exactly two accounts and prefer not to use the script:
- Distinctive: line 143
Create dirs and log in manually:
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Accounts Skill
Manages multiple Claude Code accounts using isolated CLAUDE_CONFIG_DIR directories.
One directory per account keeps auth tokens, session history, and settings separate.
Shell aliases let the user pick an account before Claude Code starts — no /logout//login needed.
Script: scripts/manage-accounts.py. Registry: ~/.claude-accounts/accounts.json.
Quick reference
| Task | Command |
| Add an account | python3 scripts/manage-accounts.py add <name> |
| Add with a named alias | python3 scripts/manage-accounts.py add work --alias cwork |
| List all accounts | python3 scripts/manage-accounts.py list |
| Validate all accounts | python3 scripts/manage-accounts.py check |
| Launch an account | python3 scripts/manage-accounts.py launch <name> |
Share skills, agents, commands from ~/.claude | python3 scripts/manage-accounts.py link [<name>] |
Register toolkit hooks in every account's settings.json | ./install.sh (vexinstall apply; see docs/installer-layout.md) |
| Install/update aliases | python3 scripts/manage-accounts.py install-aliases |
| Preview alias changes | python3 scripts/manage-accounts.py install-aliases --dry-run |
| Remove an account | python3 scripts/manage-accounts.py remove <name> |
Setup flow for 10+ accounts
1. Add accounts
python3 scripts/manage-accounts.py add work --alias cwork
python3 scripts/manage-accounts.py add personal --alias cpersonal
python3 scripts/manage-accounts.py add max1 --alias cm1
# … repeat for as many accounts as neededUse named aliases (cwork, cpersonal) rather than sequential ones (c1, c2) — named aliases are self-documenting and you won't need list to remember which is which.
Each add creates ~/.claude-accounts/<name>/, assigns the alias, installs aliases into your shell config, and links the account's skills/, agents/, and commands/ to ~/.claude.
How the toolkit reaches every account
./install.sh installs once into ~/.claude. Every account dir holds symlinks to ~/.claude/skills, ~/.claude/agents, and ~/.claude/commands, so each skill exists once and every account sees the same set. Run link (no name means all accounts) to repair an account made before this, or one where Claude Code created its own skills/ dir. link moves non-conflicting content, such as skills/synced/<account-id>/, into ~/.claude first. It stops and reports on a real conflict.
2. Log in to each account
After add, the script prints a login command. Run it once per account:
CLAUDE_CONFIG_DIR=~/.claude-accounts/work claude
# inside Claude Code: /login
# exit, then repeat for each account3. Verify
python3 scripts/manage-accounts.py list
python3 scripts/manage-accounts.py checklist shows every account including the default ~/.claude one. check validates that each registered account has credentials and shares the toolkit dirs.
4. Use
Reload your shell once, then use aliases from any terminal:
cwork # opens Claude Code with the 'work' account
cpersonal # opens Claude Code with the 'personal' account
cwork --resume # resumes the last session for the 'work' accountShell alias format
Fish (~/.config/fish/config.fish):
function cwork
set -lx CLAUDE_CONFIG_DIR "~/.claude-accounts/work"
claude --dangerously-skip-permissions --chrome --system-prompt="." $argv
endBash/Zsh (~/.bashrc / ~/.zshrc):
alias cwork='CLAUDE_CONFIG_DIR="~/.claude-accounts/work" claude --dangerously-skip-permissions --chrome --system-prompt="."'install-aliases also writes cm0, which starts the default profile (~/.claude). It runs env -u CLAUDE_CONFIG_DIR claude ...: it clears an inherited value and never sets one, because setting CLAUDE_CONFIG_DIR (even to ~/.claude) moves Claude's state off ~/.claude.json and breaks the default login. cm0 is reserved; add rejects it.
Every alias and launch pass DEFAULT_CLAUDE_ARGS from scripts/manage-accounts.py before your own arguments. Edit that tuple and re-run install-aliases to change them.
The managed block is idempotent — re-run install-aliases any time to sync after adding accounts.
Use --dry-run to preview changes before writing:
python3 scripts/manage-accounts.py install-aliases --dry-run --shell fishManual alternative (2 accounts only)
If you have exactly two accounts and prefer not to use the script:
# ~/.config/fish/config.fish
function cwork
set -lx CLAUDE_CONFIG_DIR "$HOME/.claude-accounts/work"
claude $argv
end
function cpersonal
set -lx CLAUDE_CONFIG_DIR "$HOME/.claude-accounts/personal"
claude $argv
endCreate dirs and log in manually:
mkdir -p ~/.claude-accounts/work ~/.claude-accounts/personal
CLAUDE_CONFIG_DIR=~/.claude-accounts/work claude # /login
CLAUDE_CONFIG_DIR=~/.claude-accounts/personal claude # /loginNotes
- Accounts share the same Claude Code binary and one vexjoy-agent install in
~/.claude. - Usage limits are per-subscription — no automatic failover between accounts.
- Session histories are isolated;
--resumepicks up the right history per alias. removepreserves the config directory so credentials are not accidentally deleted. To fully purge, delete the directory manually afterremove.- Shell config mutation note:
install-aliaseswrites a managed block between header/footer markers. Do not delete the markers manually; doing so causes the next run to append a second block instead of replacing. Use--dry-runto inspect before writing. - The default
~/.claudeaccount (no alias, opened by bareclaude) is always shown inlistbut not managed by this script.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

