Clausona: One Command to Switch Claude Code Accounts with All Your Plugins Intact
If you use multiple Claude Code accounts (personal, work, client projects), you know the pain: switching accounts means losing access to your carefully configured environment. Your MCP servers, plugins, and settings don't carry over. You're back to square one with each switch.
Clausona fixes this with a simple, elegant solution: profile management with automatic environment sharing.
What It Does — Symlinks Your Entire Setup
Clausona is a shell wrapper that manages multiple Claude Code profiles on a single machine. When you create a new profile, it symlinks your shared resources from your primary ~/.claude directory into the new profile's config directory.
Here's what gets shared automatically:
mcp-servers/→ All your MCP serversplugins/→ All your installed pluginssettings.json→ Your Claude Code settings
Here's what stays profile-specific:
.claude.json→ Authentication credentials (kept separate)projects/→ Session history (separate by default)
This means you install an MCP server once, and it's available across all your accounts. No more reinstalling the same tools for each profile.
Setup — Install in Seconds
Requirements: Node.js ≥20, Claude Code CLI, macOS with zsh.

curl -fsSL https://github.com/larcane97/clausona/releases/latest/download/install.sh | bash
clausona init # Discover existing Claude Code accounts
The installer registers csn as a shorthand alias for clausona and sets up the shell wrapper via eval "$(clausona shell-init)".
How To Use It — One Command Switching
# Switch to your work account
csn use work
# List all profiles with weekly usage stats
csn list
# Open the interactive dashboard
csn
When you run claude after switching profiles, the wrapper:
- Reads
~/.clausona/profiles.json - Sets
CLAUDE_CONFIG_DIRto the active profile's directory - Runs the actual
claudecommand - Tracks usage changes (cost and tokens) per profile on exit
Session Management — Separate or Shared
By default, each profile keeps its own projects/ directory. This means /resume only shows conversations from that profile—clean separation between work and personal sessions.
If you want to share session history across profiles (so you can resume any conversation from any account), Clausona supports this with a flag during profile creation.
Why It Works — No Runtime Overhead
Clausona doesn't wrap or proxy Claude Code. It runs Claude Code directly and unmodified. The entire system is:
- A single shell hook
- A few symlinks
- No daemon, no server, no runtime overhead
This makes it fully compatible with oh-my-claudecode, Cline, and any other tools in your Claude Code ecosystem.
Bonus Feature: Usage Tracking
Clausona automatically tracks cost and token usage per profile by comparing fingerprints before and after each claude invocation. Run csn list to see weekly usage breakdowns for each account—helpful for expense reporting or monitoring personal vs. work usage.
When To Install Clausona
Install Clausona if you:
- Use Claude Code for both personal projects and work
- Manage multiple client accounts
- Belong to different organizations with separate Claude Code seats
- Have invested time configuring MCP servers and plugins you want available everywhere
Don't install it if you:
- Only use one Claude Code account
- Prefer completely isolated environments for each account
- Use Windows or Linux (currently macOS/zsh only)
Clausona turns account switching from a multi-step chore into a single command while preserving your entire development environment.




