claude-dual-account-setuplisted
Install: claude install-skill bygama/workstation
# Claude Dual Account Setup
## Overview
This machine runs two Claude Code accounts off one binary. Isolation comes from
`CLAUDE_CONFIG_DIR`, which decides where credentials, sessions and usage live.
Everything meant to be shared is shared through filesystem links, not copies —
so there is one physical file, not two that need syncing.
The identity rule is: **the command decides, and everything else is pegasuz.**
A User-scope environment variable pins the machine's ambient default to the
pegasuz dir, so the only path to the personal account is typing `claude` in a
shell that loaded `$PROFILE`:
| How Claude is launched | Config dir | Bills |
| --------------------------------- | ----------------------- | -------------- |
| `claude` (function) | `~/.claude` | personal |
| `pegasuz` (function) | `~/.claude-pegasuz` | pegasuz |
| Orca and the agents it spawns | `~/.claude-pegasuz` | pegasuz* |
| bare `claude.exe`, any other tool | `~/.claude-pegasuz` | pegasuz |
\* or whatever account Orca's own switcher has placed in that dir — see the
Orca section.
The asymmetry is deliberate: any mistake, unknown launcher, or third-party
integration burns the pegasuz plan, never the personal one. The personal
account cannot be reached by accident.
The ambient default is `CLAUDE_CONFIG_DIR` at **User scope** pointing at
`~/.claude-pegasuz`. The `claude` function *clears* the va