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

@synth1s/cloak

v2.4.1

Published

Cloak your Claude. Switch identities in seconds.

Downloads

778

Readme

@synth1s/cloak

CI npm downloads license

Stop logging out. Start switching.

Every developer wears a different cloak. One for work, one for personal projects, one for that freelance gig. Cloak lets you dress your Claude Code in the right identity — and switch between them without breaking a sweat.

Sessions, tokens, MCP servers, and settings fully preserved. Concurrent sessions across terminals. 181+ developers asked for this.

demo

Before / After

Before Cloak:

claude → /logout → /login (lose session) → work on project
claude → /logout → /login (lose session) → personal use

After Cloak:

claude -a work     # instant. sessions preserved.
claude -a home     # in another terminal. at the same time.

Install

npm install -g @synth1s/cloak

3 steps to get started

# 1. Save your current Claude session
cloak create work

# 2. Log out, log in with another account in Claude, then:
cloak create home

# 3. Set up shell integration
cloak switch work    # follows the guided setup on first run

That's it. From now on:

claude -a work       # switch and launch
claude -a home       # in another terminal, at the same time

Commands

| Command | Description | |---------|-------------| | cloak create [name] | Save current session as a new cloak | | cloak switch <name> | Wear a different cloak | | cloak list | See all cloaks in your wardrobe | | cloak whoami | Which cloak are you wearing? | | cloak delete <name> | Discard a cloak | | cloak rename <old> <new> | Rename a cloak | | cloak bind <name> | Bind this directory to a cloak | | cloak unbind | Remove directory binding |

With shell integration (eval "$(cloak init)"):

| Command | Description | |---------|-------------| | claude -a <name> | Switch and launch Claude | | claude account <cmd> | All cloak commands via claude |

Concurrent sessions

Different terminal, different identity. No conflicts.

# Terminal A:
claude -a work

# Terminal B (at the same time):
claude -a home

Each account is a completely isolated directory. No file overlap, no token conflicts.

Auto-switch by directory

Bind a cloak to a project directory. Claude automatically uses the right account.

cd ~/projects/company
cloak bind work

cd ~/projects/personal
cloak bind home

From now on, claude in those directories uses the bound account — no manual switch needed.

Context bar

Every command shows which identity is active:

cloak > list . work <[email protected]> ────────────────────────────

Your Cloaks

  > work (active) — [email protected]
    home — [email protected]

How it works

Cloak uses Claude Code's official CLAUDE_CONFIG_DIR environment variable. Each account gets its own directory:

~/.cloak/
└── profiles/
    ├── work/                # complete, isolated config
    │   ├── .claude.json
    │   ├── settings.json
    │   └── ...
    └── home/
        ├── .claude.json
        └── ...

Switching changes which directory Claude Code reads from. Nothing is copied, moved, or overwritten.

FAQ

No. Each account is a completely isolated directory. Switching only changes which directory Claude Code reads from. Your settings, MCP servers, and preferences for each account stay exactly where they are.

Yes. When Claude Code renews your OAuth token during a session, it writes to the active account's directory. When you switch away and back, the renewed token is still there.

No, as long as each terminal uses a different account. Each has its own directory — no file overlap.

Cloak never transmits, logs, or modifies your tokens. It only copies files during cloak create and changes an environment variable during cloak switch. All data stays local. Credential files are created with restrictive permissions (0o600).

Your account directories remain in ~/.cloak/. Claude Code works normally with its default config. To clean up: rm -rf ~/.cloak

IDE extensions may not respect CLAUDE_CONFIG_DIR (known limitation). Cloak is designed for terminal-based Claude Code.

Requirements

  • Node.js >= 18
  • bash or zsh (for shell integration)

Contributing

See CONTRIBUTING.md.

Security

See SECURITY.md.

Documentation

License

MIT