Only the plugins, MCP servers, and skills you actually need load into each session — no bleed between contexts, ever. Each profile runs in its own CLAUDE_CONFIG_DIR.
No account. No telemetry. Works alongside your existing Claude setup.
The problem
Your work session doesn't need your personal research skills. Your personal session doesn't need your API deployment MCPs. They all load anyway — every session, you're giving a slice of your context window to tools you're not even using.
Swapping between setups meant editing ~/.claude.json and mcp.json by hand, then undoing it next session. Claude Code has no native multi-profile support.
No account. No telemetry. Works alongside your existing Claude setup.
What it does
Not config swapping. Each profile is a real isolated environment.
Each profile gets its own CLAUDE_CONFIG_DIR. MCP servers and skills from profile A physically cannot appear in profile B's session.
Find what you need without trawling GitHub. Browse 647 plugins across 114 marketplaces in one place — one search bar queries 7,009 entries at once.
Each alias cd's to its directory and optionally runs /workflow or a prefilled prompt. One profile can intercept bare claude in any terminal.
Write a /workflow body once per profile and it becomes a real Claude Code command in that session. Named variants let one profile ship multiple runbooks.
See cost, context remaining, and rate limits at a glance. 17 drag-to-reorder widgets, save configs by name, and override per-profile.
Compose a team from existing profiles. Assign roles, pick a lead, and launch. The lead spawns teammates via Claude Code's native agent-teams feature.
Get started
Requires macOS. Windows and Linux ports are planned.
Requires Node 20+ and Electron 33. Run claude login before launching — ClaudeWorks uses your existing Claude Code credentials.
No account. No telemetry. Works alongside your existing Claude setup.