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

claude-code-multi

v1.0.0

Published

Run multiple Claude Code accounts simultaneously — each in its own isolated config directory

Readme

claude-multi

A CLI tool that automates the multiple-Claude-accounts setup so you can run two (or more) Claude Code sessions simultaneously in separate terminal tabs — each with its own isolated login session.


Install

npm install -g claude-code-multi

Quick start

# 1. Run the interactive setup (animated!)
claude-multi setup

# 2. Reload your shell
source ~/.zshrc   # or source ~/.bashrc

# 3. Authenticate each account (do this once per account)
claude-personal   # launches Claude → run /login
claude-work       # launches Claude → run /login

# 4. Code in parallel — open two terminal tabs:
#   Tab 1: claude-personal
#   Tab 2: claude-work

Both sessions are 100% isolated — separate logins, separate history, separate settings.


Commands

| Command | Aliases | What it does | |---|---|---| | claude-multi setup | install | Animated setup: names your accounts, writes shell aliases to .zshrc | | claude-multi add [name] | new, create | Add another account | | claude-multi list | ls | Show all accounts and whether each is logged in | | claude-multi remove <name> | rm | Delete an account and its config dir | | claude-multi uninstall | | Remove all managed aliases from .zshrc / .bashrc | | claude-multi help | --help, -h | Show usage |


How it works

Claude Code stores its login session in ~/.claude by default. Set CLAUDE_CONFIG_DIR to any path and Claude uses that directory instead — completely independent from any other account.

claude-multi setup automates all the manual steps:

  1. Finds your real claude binary path automatically
  2. Creates ~/.claude-multi/<name>/ for each account
  3. Writes shell aliases to .zshrc / .bashrc:
alias claude-personal='CLAUDE_CONFIG_DIR=~/.claude-multi/personal /usr/local/bin/claude'
alias claude-work='CLAUDE_CONFIG_DIR=~/.claude-multi/work /usr/local/bin/claude'
alias claude='echo "Use a specific account: claude-personal, claude-work"'

The last alias overrides bare claude with a helpful reminder so you never accidentally launch the wrong account.


Running accounts in parallel

Open two terminal tabs and run a different account in each:

Tab 1                           Tab 2
─────────────────────────────── ───────────────────────────────
$ claude-personal               $ claude-work
> working on side project       > working on client code
  completely isolated session     completely isolated session

Both run simultaneously. One account hitting a rate limit doesn't affect the other — just switch tabs and keep going.


Add more accounts

claude-multi add freelance
source ~/.zshrc
claude-freelance   # then /login

Per-project default account

Add this to your project's .env (works with direnv or similar):

CLAUDE_CONFIG_DIR=~/.claude-multi/work

Claude Code will automatically use the work account in that project.


Uninstall

# Remove aliases from .zshrc / .bashrc
claude-multi uninstall

# Remove all account data (optional)
rm -rf ~/.claude-multi

# Remove the npm package
npm uninstall -g claude-code-multi

Contributing

Bug reports and pull requests welcome at GitHub.

Keep it plain JavaScript (ESM), no build step, minimal dependencies.


License

MIT