HN Showcase
Back to browse
GitHub Repository

CLI tool to manage multiple Claude Code profiles

36 starsTypeScript

Clausona – Manage multiple Claude Code accounts, keep all your settings

by larcane·Mar 9, 2026·3 points·0 comments
Visit ProjectView on HN

AI Analysis

●●SolidSolve My ProblemCozy

Symlinks shared MCP servers so you don't reconfigure plugins when switching Claude Code accounts.

Strengths
  • •Symlinks shared resources so MCP servers and plugins don't need reinstallation per account.
  • •Shell hook swaps CLAUDE_CONFIG_DIR without proxying or modifying the Claude Code binary.
  • •Local usage tracking shows token costs per profile without sending data externally.
Weaknesses
  • •macOS and zsh only right now, excluding Windows and bash users entirely.
  • •Relies on Claude Code's internal config structure staying stable across future updates.
Target Audience

Developers using Claude Code CLI with multiple accounts

Similar To

direnv · AWS CLI · oh-my-claudecode

Post Description

I've been using Claude Code with multiple accounts (personal + work) and got tired of re-setting up MCP servers, plugins, and permissions for each one.

Settings don't carry over, and switching means logging out or manually managing CLAUDE_CONFIG_DIR.

So I made a simple tool for it. Clausona sets CLAUDE_CONFIG_DIR via a shell hook and symlinks shared resources (plugins, MCP servers, settings) from your primary config.

Auth stays separate per profile. No wrapping or proxying. Claude Code runs directly.

Curious if others have dealt with this and what pain points you've run into.

Thanks for any feedback!

Similar Projects