npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@ghackk/multi-claude

v1.0.23

Published

Run multiple Claude CLI accounts with shared settings, plugins, marketplace sync, and backup/restore

Downloads

2,396

Readme


Why?

Claude CLI stores all config in a single ~/.claude/ directory — so you're locked to one account at a time. Switching means logging out, logging in, and losing your settings.

claude-multi-account fixes this:

  • Isolated profiles — each account gets its own config directory, no conflicts
  • Shared settings — define MCP servers, env vars, plugins, and CLAUDE.md once — auto-applied everywhere
  • Plugin & marketplace management — enable plugins globally or per-account, browse marketplace indexes
  • Direct launch — run claude-work or claude-personal directly from any terminal, no menu needed
  • Cloud backup & restore — securely sync all profiles to the cloud and restore on any machine
  • One command — launch any account instantly from an interactive menu

Features

Multi-Account Management Create, launch, rename, and delete independent Claude CLI profiles

Shared MCP & Settings Define MCP servers, env vars, and preferences once — sync to all accounts

Plugins & Marketplace Enable/disable plugins globally or per-account, browse and manage marketplace indexes

Global CLAUDE.md Write instructions and skills that apply across every account

Backup & Restore Timestamped local archives of all accounts and configs with one click

Export / Import Profiles Copy a profile between machines as a single base64 token — credentials, settings, and launcher included

Cloud Backup & Restore Securely sync all profiles to the cloud — restore on any machine with a single command

Direct Profile Launch Each profile is auto-registered on PATH — run claude-work directly from any terminal

Auto Dependency Detection Detects and offers to install missing dependencies (curl, jq, etc.) on first run

Run from Repo Add the repo to your PATH — git pull instantly updates the menu, no manual copying


Install

Pick any method — they all give you the claude-menu (or multi-claude) command.

One-liner (recommended)

# Linux / macOS
curl -fsSL https://raw.githubusercontent.com/ghackk/claude-multi-account/master/install.sh | bash
# Windows (PowerShell)
irm https://raw.githubusercontent.com/ghackk/claude-multi-account/master/install.ps1 | iex

npm

npm install -g @ghackk/multi-claude

pip

pip install multi-claude

Homebrew (macOS / Linux)

brew install ghackk/tap/multi-claude

Scoop (Windows)

scoop bucket add multi-claude https://github.com/ghackk/scoop-multi-claude
scoop install multi-claude

AUR (Arch Linux)

yay -S multi-claude

Manual (git clone)

# Linux / macOS
git clone https://github.com/ghackk/claude-multi-account.git ~/claude-multi-account
echo 'alias claude-menu="~/claude-multi-account/unix/claude-menu.sh"' >> ~/.bashrc
# Windows
git clone https://github.com/ghackk/claude-multi-account.git $HOME\claude-multi-account
[Environment]::SetEnvironmentVariable("PATH", "$HOME\claude-multi-account;" + [Environment]::GetEnvironmentVariable("PATH", "User"), "User")

Then open a new terminal and run claude-menu.


Menu Overview

Main Menu

======================================
       Claude Account Manager
======================================
  Current Accounts:

  1. claude-work     [logged in]   (last used: 02 Mar 2026 10:30 AM)
  2. claude-personal [logged in]   (last used: 01 Mar 2026 08:15 PM)

======================================
  1. List Accounts
  2. Create New Account
  3. Launch Account
  4. Rename Account
  5. Delete Account
  6. Backup Sessions (Local)
  7. Restore Sessions (Local)
  8. Shared Settings (MCP/Skills)
  9. Plugins & Marketplace
  E. Export Profile (Token)
  I. Import Profile (Token)
  C. Cloud Backup
  R. Cloud Restore
  0. Exit
======================================

Shared Settings (Option 8)

Manage universal settings applied to all accounts on launch:

| Option | Action | |--------|--------| | 1 | Edit MCP + Settings (opens in editor) | | 2 | Edit Skills/Instructions (CLAUDE.md) | | 3 | View current shared settings | | 4 | Sync shared settings to ALL accounts | | 5 | Show MCP server list | | 6 | Reset shared settings |

Plugins & Marketplace (Option 9)

Browse marketplace indexes and manage plugins across accounts:

| Option | Action | |--------|--------| | 1 | Enable plugin for ALL accounts | | 2 | Enable plugin for one account | | 3 | Disable plugin (shared) | | 4 | Disable plugin (one account) | | 5 | Browse marketplace plugins | | 6 | Marketplace Management (add/remove/sync) |

Export / Import Profile (Options E & I)

Transfer a profile between machines using a copy-pasteable base64 token:

| Option | Action | |--------|--------| | E | Export a profile — generates a compact token (~5 KB) containing credentials, settings, and launcher | | I | Import a profile — paste the token to restore the account on any machine |

The token bundles only essentials (credentials, settings, CLAUDE.md, launcher) — not cache or conversation history.

Cloud Backup & Restore (Options C & R)

Sync all profiles to the cloud and restore on any machine:

| Option | Action | |--------|--------| | C | Cloud Backup — select profiles and optional folders (shared settings, plugins, etc.) to upload securely | | R | Cloud Restore — enter your route key to download and restore all profiles on a new machine |

Profiles are automatically registered on PATH after restore, so you can run claude-work immediately.

Direct Profile Launch

Every profile you create is automatically available as a command:

# No need to open the menu — just run the profile name directly
claude-work
claude-personal

On Linux/macOS/Termux, symlinks are created in ~/.local/bin/. On Windows, the accounts directory is added to your user PATH. Profiles created, imported, or restored are all registered automatically.


How It Works

┌─────────────┐      ┌──────────────────┐      ┌─────────────────┐
│  You pick    │ ───> │  Shared settings │ ───> │  Claude CLI     │
│  an account  │      │  + plugins are   │      │  launches with  │
│  from menu   │      │  merged in       │      │  isolated config│
└─────────────┘      └──────────────────┘      └─────────────────┘

Each account gets its own config directory (~/.claude-<name>). On every launch, shared settings from ~/claude-shared/ are deep-merged into the account — MCP servers, env vars, preferences, plugins, marketplace indexes, and CLAUDE.md instructions all stay in sync.

Merge Strategy

Settings are deep-merged with shared settings winning on conflict:

| Scenario | Result | |----------|--------| | Key exists only in account | Kept | | Key exists only in shared | Added | | Key exists in both (simple value) | Shared wins | | Key exists in both (nested object) | Recursively merged |

For CLAUDE.md, shared content is inserted between auto-managed markers at the top. Account-specific instructions below the markers are preserved.


Folder Structure

~/
├── claude-multi-account/      # Git repo (can be added to PATH directly)
│   ├── claude-menu.ps1        # Windows menu script
│   ├── claude-menu.bat        # Windows launcher
│   ├── windows/               # Windows-specific scripts
│   └── unix/                  # Linux/macOS scripts
│
├── claude-accounts/           # Account launchers (auto-created)
│   ├── claude-work.bat/.sh    # Account launcher
│   └── claude-personal.bat/.sh
│
├── claude-shared/             # Shared config (applied to all accounts)
│   ├── settings.json          # MCP servers, env vars, preferences, enabledPlugins, extraKnownMarketplaces
│   ├── CLAUDE.md              # Global instructions & skills
│   └── plugins/               # Shared plugin & marketplace data
│       └── marketplaces/      # Cached marketplace indexes
│
├── claude-backups/            # Timestamped backup archives
│
├── .claude-work/              # Account: work (auto-created)
├── .claude-personal/          # Account: personal (auto-created)
└── .claude-<name>/            # Account: <name>

Documentation


Requirements

  • Claude CLI installed and available in PATH
  • Windows: PowerShell 5.1+ (dependencies auto-detected via winget/scoop)
  • Linux/macOS: Bash 4+ (dependencies like curl, jq auto-detected and offered for install on first run)
  • Termux: Supported — dependencies installed via pkg

Contributing

Contributions are welcome! Feel free to open an issue or submit a pull request.


Credits

Built by Gyanesh Kumar


License

MIT