Accounts logo

Accounts

Community
notque
accounts

Manage multiple Claude Code accounts: add, list, check, launch, and install shell aliases for 10+ isolated CLAUDE_CONFIG_DIR profiles.

Overview

Publishernotque
Repositoryvexjoy-agent
Skill nameaccounts
Stars
443
Forks
50
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by notque on GitHub. Read the source before you install it.

Installation

Install the Accounts AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/notque/vexjoy-agent/tree/main/skills/meta/accounts
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/notque/vexjoy-agent.git /tmp/vexjoy-agent
mkdir -p .claude/skills
cp -r /tmp/vexjoy-agent/skills/meta/accounts .claude/skills/accounts
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Accounts in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Accounts on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Accounts is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

TaskCommand
Add an accountpython3 scripts/manage-accounts.py add <name>
Add with a named aliaspython3 scripts/manage-accounts.py add work --alias cwork
List all accountspython3 scripts/manage-accounts.py list
Validate all accountspython3 scripts/manage-accounts.py check
Launch an accountpython3 scripts/manage-accounts.py launch <name>
Share skills, agents, commands from ~/.claudepython3 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 aliasespython3 scripts/manage-accounts.py install-aliases
Preview alias changespython3 scripts/manage-accounts.py install-aliases --dry-run
Remove an accountpython3 scripts/manage-accounts.py remove <name>

Setup flow for 10+ accounts

1. Add accounts

bash
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 needed

Use 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:

bash
CLAUDE_CONFIG_DIR=~/.claude-accounts/work claude
# inside Claude Code: /login
# exit, then repeat for each account

3. Verify

bash
python3 scripts/manage-accounts.py list
python3 scripts/manage-accounts.py check

list 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' account

Shell alias format

Fish (~/.config/fish/config.fish):

fish
function cwork
    set -lx CLAUDE_CONFIG_DIR "~/.claude-accounts/work"
    claude --dangerously-skip-permissions --chrome --system-prompt="." $argv
end

Bash/Zsh (~/.bashrc / ~/.zshrc):

bash
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:

bash
python3 scripts/manage-accounts.py install-aliases --dry-run --shell fish

Manual alternative (2 accounts only)

If you have exactly two accounts and prefer not to use the script:

fish
# ~/.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
end

Create dirs and log in manually:

bash
mkdir -p ~/.claude-accounts/work ~/.claude-accounts/personal
CLAUDE_CONFIG_DIR=~/.claude-accounts/work claude   # /login
CLAUDE_CONFIG_DIR=~/.claude-accounts/personal claude  # /login

Notes

  • 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; --resume picks up the right history per alias.
  • remove preserves the config directory so credentials are not accidentally deleted. To fully purge, delete the directory manually after remove.
  • Shell config mutation note: install-aliases writes 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-run to inspect before writing.
  • The default ~/.claude account (no alias, opened by bare claude) is always shown in list but not managed by this script.

Frequently asked questions

What does the Accounts AI skill do?

Manage multiple Claude Code accounts: add, list, check, launch, and install shell aliases for 10+ isolated CLAUDE_CONFIG_DIR profiles.

Why use Accounts on TypingMind?

Because you install it once and use it with any model. Accounts is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Accounts in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/notque/vexjoy-agent/tree/main/skills/meta/accounts. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Accounts?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Accounts?

As many as you like. As long as a model supports skills, you can use Accounts with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Accounts AI skill free?

Yes. It is published on GitHub by notque under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇