claude-multiprofile CLI

A macOS CLI that creates isolated Claude Desktop and Claude Code profiles, each with its own login, chats, settings and icon.

  • 199 ★ on the repository
  • Last commit
  • MIT
CLI

Extended access

Why this level

  • The utility copies the Claude app, appends aliases to shell files and changes profile settings on your computer.
All reasons and checks

jmdarre-v/claude-multiprofile

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add cli/claude-multiprofile

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The utility copies the Claude app, appends aliases to shell files and changes profile settings on your computer.

This is third-party code. Review the repository files before installing.

What it does

claude-multiprofile automates the manual setup for several Claude accounts: personal, work and client. For Desktop it makes an app copy with a separate `--user-data-dir` and a Dock icon, and for Claude Code it sets `CLAUDE_CONFIG_DIR` and adds an alias such as `claude-work` to the shell profile. Each profile has its own login, chats, MCP servers, plugins and skills. `claude-multiprofile add` creates a profile, while `doctor` finds what drifted after a Claude update or a shell change, including a profile open under the wrong account, and repairs the safe parts with `doctor --fix`. There are also `list`, `status`, `rename`, `remove` and `upgrade`. Claude Code settings can be copied at creation without conversations or sign-in.

Who it is for. Freelancers and consultants on macOS who run personal, work and client Claude accounts at the same time.

Good fit when

  • Two Claude accounts serve different projects and signing out of one for the other has become tedious.
  • Client work has to stay in its own profile with its own MCP servers and skills.
  • After a Claude update a profile icon broke or an alias points the wrong way.
  • Claude Code settings were carried to a new profile without copying history or sign-in.

Not a fit when

  • The platform is Linux or Windows and a Desktop profile is needed: Desktop profiles require macOS.
  • You need official multi-account support: the author calls the approach unofficial.
  • The profiles would be used to get around one account's limits: the tool is meant for separate personal, work and client access.

Example request

Create a `work` profile for Claude Desktop and Claude Code, copy my Claude Code settings without conversations and show the terminal alias.

Limitations

The tool is unofficial and relies on the public Electron flag `--user-data-dir` and the little-documented `CLAUDE_CONFIG_DIR` variable. If a new Claude release changes how profiles work, an update will be needed. Desktop profiles work on macOS only and Claude Code profiles on macOS and Linux. Node.js 18 or newer is required. You read Claude's terms for multi-account use yourself: the tool does not change them or lift responsibility for access.

How to disable. Remove profiles with `claude-multiprofile remove`, then the package itself with `npm uninstall -g claude-multiprofile`. The original Claude stays untouched.

FAQ

How do I install claude-multiprofile?

Run `npm install -g claude-multiprofile` and then `claude-multiprofile add`. The utility creates the profile, a Dock icon and a terminal alias.

What does a profile isolate?

Login, chats, settings, MCP servers, plugins and skills. Each profile has its own Dock icon and its own terminal command, for example `claude-work`.

What does the doctor command do?

`claude-multiprofile doctor` looks for drift after Claude updates and shell changes, including a profile open under the wrong account. `doctor --fix` applies the safe repairs.

How do I update the tool?

`claude-multiprofile upgrade` installs the latest version and then applies its changes to your profiles. The `--no-fix` flag limits it to installation.

Does it affect my main Claude?

No. Profiles are created alongside it and the main Claude stays untouched.

Discussion

No questions or reviews yet.

CLI tools
Needs a VPN

A Linux and macOS CLI that keeps a separate Claude Code profile per account and switches work, personal and SSO in one command

CLIExtended access79Repository stars

claude-transplant moves Claude Code sessions between Claude Desktop accounts so the sidebar stays full after a switch.

CLIExtended access54Repository stars

A local web editor for Claude Code config: shows project sizes, deletes old chat histories and manages MCP servers

CLIExtended access266Repository stars

A Claude Code panel for several projects: statuses, button decisions, Git, PR, CI and usage limits in one window.

PluginExtended access79Repository stars

A macOS menu bar indicator that shows whether Claude Code is thinking, waiting for your permission and how long the current turn has run

PluginExtended access732Repository stars

claude-sync encrypts and syncs Claude Code sessions between computers through R2, S3, GCS or WebDAV.

CLIExtended access324Repository stars

Comparison with similar tools

Cards that share the main search query, and how they differ.

ToolOfficialRepository starsMain difference
claude-multiprofile (this card)no199
CC Switchno153,939switches providers and Claude Code configs; claude-multiprofile splits accounts into isolated profiles together with Claude Desktop
Codex Profilesno94profiles for Codex; this one covers Claude Desktop and Claude Code

README in short

The utility wraps the manual profile setup into one command: app copy, icon, rc-file alias and a profile registry. A step-by-step session lives in `examples/walkthrough.md`.

README badge

Report a problem