aiacc

README

aiacc

One command per AI-CLI account.

Keep your personal, work, and client accounts for Claude Code, Codex, and any other AI CLI side by side — each in its own isolated config — and launch any of them by name.

$ claude-work        # opens Claude Code signed in as your work account
$ claude-personal    # …a different account entirely — no re-login, no juggling

Bare aiacc opens an interactive launcher:

┏━ AIACC ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃                                              ┃
┃   ▄▀█ █ ▄▀█ █▀▀ █▀▀                          ┃
┃   █▀█ █ █▀█ █▄▄ █▄▄                          ┃
┃   // launch a profile                        ┃
┣━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┫
┃  ▸ claude-work          carlos@work.io       ┃
┃    claude-personal      not logged in        ┃
┃    ⚠ old                dir missing          ┃
┣━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┫
┃  ◆ 3 profiles   ✓ ready                      ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
  ↑↓ move  ⏎ launch  a add  r rename  h hand off  d remove  q quit

Hacker / matrix-terminal skin — phosphor green on black, a > prompt with a blinking cursor and cyan hotkeys, a » N profiles :: ✓ READY status readout, and a live AIACC logo (dark-green → bright-green → cyan sweep) that glitches in short data-tear bursts, plus a reverse-video glow on the selected row. Add / rename / remove / hand off / setup all happen in-screen. Honors NO_COLOR.

Responsive — the frame follows the terminal: it grows and narrows with the width, re-measures live on resize, and a profile list taller than the window scrolls inside the box (▲ n above · ▼ n below) instead of spilling out of it.

---

✨ Why aiacc

• 🔀 One command per account — claude-work opens Claude Code signed into that account. No env juggling, no re-login.
• ⚡ One-step setup — aiacc setup installs the commands onto your PATH; they work immediately, in the shell you're already in. No sourcing, no reload.
• 🧭 Interactive picker — a bare aiacc gives you an arrow-key list to launch, add, rename, or remove accounts.
• 🧩 Same skills everywhere — every profile shares your skills, sub-agents, slash commands and hooks, so claude-work is the same tool as claude, not an empty one.
• 🔒 Never touches your credentials — aiacc only points an environment variable at a config directory; each account's login stays in its own dir.
• 🪶 Zero dependencies — a single static Go binary. Nothing to install alongside it.
• 🛟 Hard to misuse — junk names can't be entered, broken profiles can't be launched, and destructive actions ask first.

How it works (one generic mechanism)

Each account is an isolated config directory, selected by an environment variable. Claude Code reads CLAUDE_CONFIG_DIR; point it at ~/.claude-work and Claude runs as your work account, at ~/.claude-personal and it's the personal one. aiacc registers those directories and installs a launcher command per account that runs CLAUDE_CONFIG_DIR=<dir> claude for you — scoped to that one launch, with no global state to get out of sync.

📦 Install

# Go toolchain
go install github.com/CarlosDanielDev/aiacc@latest

# Install script (latest release binary → /usr/local/bin or ~/.local/bin)
curl -fsSL https://raw.githubusercontent.com/CarlosDanielDev/aiacc/main/install.sh | sh

# Homebrew
brew install CarlosDanielDev/tap/aiacc

🚀 Quick start

# 1 · Add a couple of accounts (run `aiacc` and press `a`, or use flags):
aiacc add claude claude-work     --dir ~/.claude-work
aiacc add claude claude-personal --dir ~/.claude-personal

# 2 · Install the launcher commands — one step, works right away:
aiacc setup

# 3 · Launch by name:
claude-work

The name you give an account is its launcher command — so name it how you want to type it (claude-work, claude-client-x, …). Names are limited to letters, digits, - and _, since they must be valid shell command names.

The first time you launch a fresh account, Claude Code opens signed out — run /login inside it once, and that account's directory remembers it from then on.

⚡ Setup, in one step

aiacc setup

That's the whole thing. aiacc setup installs a small executable per account (claude-work, …) into a directory on your PATH, so the commands work immediately, in the shell you're already in — no sourcing, no reload, no new terminal. It's idempotent (safe to re-run), and aiacc add / aiacc remove / aiacc rename keep the commands in sync automatically.

In the rare case that no writable directory is already on your PATH, aiacc installs into ~/.local/bin and adds it to your PATH — the one situation where you'll open a new terminal to finish.

Prefer shell functions over executables?

aiacc shell-init <shell> prints them, if you'd rather add a line to your startup file yourself:

eval "$(aiacc shell-init bash)"        # ~/.bashrc
eval "$(aiacc shell-init zsh)"         # ~/.zshrc
aiacc shell-init fish | source         # ~/.config/fish/config.fish

🧩 Same skills in every profile

A profile is an isolated config directory — and everything the CLI discovers lives in that directory. Point CLAUDE_CONFIG_DIR somewhere new and Claude Code starts with no skills, no sub-agents, no slash commands and no CLAUDE.md: the same binary, a much emptier tool.

aiacc setup fixes that in the same step, and aiacc link does it on demand:

aiacc link                    # share with every profile
aiacc link claude work        # …or just one
aiacc link --replace          # take over entries a profile already has

It symlinks your authored assets out of the CLI's own config dir, so they stay in one place — edit a skill once and every profile has it:

Provider	Shared
claude (~/.claude)	skills/ · agents/ · commands/ · hooks/ · output-styles/ · plugins/ · CLAUDE.md · settings.json
codex (~/.codex)	prompts/ · AGENTS.md

What is never shared: credentials, projects/ transcripts, history.jsonl, usage counters — isolating those is the whole point of a profile.

Nothing is overwritten. An entry a profile already has of its own is left exactly as it is and reported instead. --replace opts into taking it over, and even then the original is renamed to <name>.aiacc-bak first, never deleted. Custom (non-preset) providers are skipped — aiacc doesn't guess at a CLI's asset layout.

🎛️ Commands

Command	What it does
aiacc	The interactive picker (front door). Piped/redirected, it prints help instead.
<account>  e.g. claude-work	Launch Claude Code in that account (installed by aiacc setup).
aiacc setup	One-step install of the launcher commands onto your PATH — they work immediately.
aiacc add [provider] [account] --dir <path>	Register an account (framed screen with no args in a terminal). Creates the dir if missing. For a non-preset provider, add --env <ENV_VAR> --command <cli>.
aiacc rename <provider> <old> <new>	Rename an account and its launcher command, keeping its directory. (picker: r)
aiacc remove <provider> <account>	Unregister an account; leaves the directory in place. (picker: d)
aiacc handoff [provider] [from] [to]	Copy a session between accounts to resume it there. No args → interactive picker; --session <id>, --launch. (picker: h)
aiacc link [provider] [account]	Share your skills, sub-agents, commands and hooks with a profile (all of them by default). --replace takes over entries a profile owns.
aiacc list	Table of providers and their accounts.
aiacc status	Which config dir each provider's env var currently points at.
aiacc usage [provider]	Token totals per account, from local session logs.
aiacc shell-init <bash|zsh|fish>	Print the per-account launcher functions (alternative to setup).

⚙️ Configuration

State lives in a single TOML file at ~/.config/aiacc/config.toml ($XDG_CONFIG_HOME is honored). add / remove / rename write it for you, but it's plain text you can edit by hand:

[providers.claude]
env_var = "CLAUDE_CONFIG_DIR"

[providers.claude.accounts.claude-personal]
dir = "~/.claude-personal"

[providers.claude.accounts.claude-work]
dir = "~/.claude-work"

A leading ~ in a dir expands to your home directory. A missing config file is treated as empty, so read-only commands work before you register anything.

🎬 Tutorials

1 · Two accounts in a minute

# Register work + personal (each gets its own isolated config dir):
aiacc add claude claude-work     --dir ~/.claude-work
aiacc add claude claude-personal --dir ~/.claude-personal

# Install the launcher commands (one step, works immediately):
aiacc setup

# Launch — the first run opens Claude signed out; do /login once:
claude-work        # → /login as work
claude-personal    # → /login as personal

From now on, claude-work always opens Claude Code as work, claude-personal as personal. No switching, no re-login.

2 · Hit a usage limit? Continue on your other account

You're deep in a conversation on claude-work and it hits the cap. Hand the exact session to claude-personal and keep going:

aiacc handoff              # interactive: pick source → session → target
# or go straight there:
aiacc handoff claude claude-work claude-personal --launch

It copies just the session transcript into the other account and resumes it — same context, now billed to personal. (In the picker, press h on the source account.)

3 · Rename a command

Named it claude-work but want claude-acme? In the picker, highlight it and press r — or:

aiacc rename claude claude-work claude-acme

The account, its directory, and the launcher command all move together; the old claude-work command is removed.

4 · Add a client account later

aiacc add claude claude-acme --dir ~/.claude-acme

The claude-acme command is created immediately (no re-setup needed), and shows up in the picker next time you run aiacc.

⌨️ Picker keys

Key	Action	Key	Action
↑ ↓ / j k	move	a	add a profile
⏎	launch the selected profile	r	rename
h	hand off a session	d	remove (asks first)
s	run setup	q / esc	quit

On any screen that ends in a command to run — the hand-off result, for one — ctrl-c copies it to your clipboard instead of closing (q still closes). Uses pbcopy, wl-copy, xclip or xsel, whichever you have.

🔗 Share a session across accounts

Hit a usage limit mid-conversation? Hand the exact session to another account and keep going:

$ aiacc handoff claude claude-work claude-personal
Handed off session 2f1c… → claude-personal
  "Fix the launcher"
Resume it:
  cd ~/projects/aiacc && claude-personal --resume 2f1c…

Claude Code keeps each session as a transcript at <config-dir>/projects/<cwd>/<id>.jsonl. handoff copies that transcript into the target account (preserving its project directory) and prints the exact resume command — --launch runs it for you, or ctrl-c on the result screen copies it. Only the transcript moves; credentials are never touched, and each account's usage stays separate. It defaults to the most recent session; --session <id> picks a specific one.

🔌 Providers — any AI CLI

A provider is {env_var, command} plus its accounts: aiacc isolates each account in its own directory, points the CLI's config-dir env var at that directory, and runs the command there. Built-in presets:

Provider	Env var	Command
claude	CLAUDE_CONFIG_DIR	claude
codex	CODEX_HOME	codex

Any other CLI that selects its config through an environment variable works too — just give the env var and command the first time you add one for that provider:

aiacc add glab work --dir ~/.glab-work --env GLAB_CONFIG_DIR --command glab
#         provider account                    ^env var        ^cli to launch
# → a `work` command that runs: GLAB_CONFIG_DIR=~/.glab-work glab

In the picker, pressing a lets you choose the provider (presets + any you've already configured) and defaults the directory to ~/.<provider>-<name>. A brand-new custom provider is added with the --env/--command form above.

Session hand-off is Claude-specific for now — it reads Claude Code's transcript format. Launch, add, rename, remove, and setup work for every provider.

🩺 Troubleshooting

claude-work: command not found

The launcher commands aren't installed yet, or the shell they were installed for isn't this one. Run aiacc setup (it prints where it put them and whether they work now). If it had to add a directory to your PATH, open a new terminal.

Upgraded from an old version and see unknown flag: --shell

A pre-v0.7 shell hook is still loaded. Just run aiacc (it prints the fix) or open a new terminal — the launcher commands replace the old hook.

A profile shows ⚠ no launcher in the picker

That provider isn't Claude, and aiacc only knows how to launch the claude CLI so far. The profile is still registered; launch commands for other providers are a planned addition.

🤝 Contributing

Public and open to contributions. Read CONTRIBUTING.md and the architecture decision records first.

📄 License

MIT © CarlosDanielDev

Documentation

Overview

Command aiacc switches and monitors multiple AI-CLI accounts via per-account config directories and environment variables.