al-mo.de › mcl
Stop logging out and back in. mcl gives each account its own isolated config, history and settings — and runs them side by side.
uv tool install git+https://github.com/mkalmousli/mcl
Separate login, history and settings per instance via CLAUDE_CONFIG_DIR. Nothing leaks between work and personal.
Run two accounts in two terminals at the same time. No logout, no lost context.
--share links your settings, CLAUDE.md, commands, agents and skills while logins stay private.
Every session shows a bold MCL · name badge in a two-line status bar: model, git branch, cost, context, cache and plan limits. On by default; mcl statusline work off turns it off.
Every claude flag passes straight through. mcl work -c just works.
mcl ls shows each instance, its account email and when you last used it.
Tiny, pure Python, MIT licensed. Linux, macOS and Windows. Installs in seconds with uv or pipx.
Yes. Each mcl instance sets its own CLAUDE_CONFIG_DIR, so you can run different logins in different terminals simultaneously.
Create an instance per account with mcl new work, then start it with mcl work. Each one keeps its own login, so there is nothing to switch.
Only if you ask. mcl new name --share links settings.json, CLAUDE.md, commands, agents and skills from ~/.claude. Logins and history always stay separate.
The status line starts with a bold MCL badge and the instance name, for example MCL · work. Turn it off with mcl statusline name off.
In ~/.mcl/<name> by default. Set MCL_HOME to change it.
Yes, fully free and open source under the MIT license.
Linux, macOS and Windows with Python 3.9 or newer.
No. It is an independent open-source tool that launches the official claude CLI.