claude-rig

Run multiple Claude Code configurations side by side.

The Problem

Claude Code keeps all configuration in a single `~/.claude/` directory. That works until you need:

• Multiple subscriptions -- You have 2-5 Max accounts and have to log out and back in every time you switch. No way to run two subscriptions at the same time.
• API and subscription side by side -- Want API access for one project and your Max subscription for another? Same deal -- one config, one auth.
• Different tools per project -- Your web project needs Tailwind skills and a database MCP server. Your CLI tool needs none of that. But every session loads the same plugins, MCP servers, and hooks.
• Testing without risk -- Want to try a new MCP server without it leaking into your production setup? You'd have to disable everything else, test, then re-enable. No isolation.

What claude-rig Does

Each configuration becomes its own isolated **rig** -- separate settings, skills, plugins, agents, commands, hooks, MCP servers, and instructions. Auth can be shared across rigs or kept separate. Run the