Public npm utility · v0.2.1

One terminal.
Clearer lanes.

Run separately authorized Claude Code profiles from direct commands—each with its own configuration directory, while your default profile stays untouched.

Install globally Node.js 22+
npm install -g @nathanpixodeo/claude-profile-manager

Independent project. Not affiliated with, endorsed by, sponsored by, or maintained by Anthropic.

ROUTING MAP / LOCAL MACHINE
The native claude command uses the default profile, while generated commands route to isolated team and studio profile directories.
~/project — shell 80×24

The manager sets one documented environment variable, then launches your installed claude executable.

0runtime dependencies

3desktop platforms

1variable routed

100%local profile paths

01 / WHY

Less profile friction.
More context control.

Useful separation without a second terminal setup, proxy, or background service.

Commands you remember

Create launchers like claude-team or claude-studio. Claude arguments and exit codes pass through.

Sharing stays explicit

Sessions and skills remain separate unless you choose to link them. Existing directories require an explicit backup flag.

02 / WORKFLOW

Install. Name. Launch.

Three deliberate steps. No daemon and no shell framework.

  1. 01

    Install the CLI

    Use the public npm package on Node.js 22 or newer.

    npm i -g @nathanpixodeo/claude-profile-manager
  2. 02

    Add an authorized profile

    Create its local directory and, optionally, a direct launcher.

    claude-profiles add team --command claude-team --login
  3. 03

    Work in its lane

    Run from any project directory and pass normal Claude Code flags.

    claude-team --continue

03 / WHERE

Same contract.
Native launchers.

One CLI model, adapted to each platform's global npm executable layout.

Windows

Windows 10, 11, and Server

Managed .cmd launchers

Linux

Node.js-supported distributions

Executable POSIX launchers

macOS

Node.js-supported versions

Executable POSIX launchers
claude-profiles doctor

Checks Node.js, npm, Claude Code, profile storage, and command directory readiness.

04 / BOUNDARIES

Separation is a tool.
Not a loophole.

Use only accounts you own or are explicitly authorized to administer. Every profile remains subject to current Anthropic terms, policies, limits, and regional access rules.

  • The CLI does not print, copy, move, bundle, or delete credentials.
  • Authentication stays inside Claude Code's official login flow.
  • Separate directories do not change billing, rate limits, bans, or safeguards.
  • Do not share credentials or link data across unauthorized people or organizations.

05 / QUESTIONS

Before you route.

Does this replace the official Claude Code CLI?

No. It launches the claude executable already installed on your machine and sets the documented CLAUDE_CONFIG_DIR variable for named profiles.

Does a profile increase subscription or rate limits?

No. Profile directories do not aggregate, extend, evade, or alter billing, subscription allowances, rate limits, bans, safeguards, or product restrictions.

Are sessions and skills shared?

Not by default. You may explicitly link them only when the same person or authorized organization controls both contexts and the data may be disclosed in both.

What happens when I uninstall?

Use claude-profiles command clean first to remove generated launchers. Uninstalling keeps profile directories, command mappings, sessions, state, and credentials.

Is this an Anthropic product?

No. This is an independent, unofficial third-party utility. It is not affiliated with, endorsed by, sponsored by, or maintained by Anthropic.

LOCAL ROUTING / CLEAR CONTEXTS

Give each authorized profile
its own front door.

npm install -g @nathanpixodeo/claude-profile-manager