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

clauda

v0.2.0

Published

Launch Claude Code with per-profile API endpoints (base URL + API key), without touching your subscription login

Readme

clauda

Launch Claude Code against different API endpoints — without touching your subscription login.

  • Plain claude → keeps using your logged-in subscription account, as always.
  • clauda <profile> → launches Claude Code with that profile's ANTHROPIC_BASE_URL + API key (token-billed), e.g. the official API, a corporate gateway, or any Anthropic-compatible provider (Kimi, GLM, …).

Each profile gets its own isolated CLAUDE_CONFIG_DIR, so your ~/.claude subscription login is never mixed with API-key sessions, and you never get the "API key vs subscription" conflict prompt.

Install

npm install -g clauda

Requires macOS or Linux with bash, and the claude CLI installed.

Quick start

# Create a profile (the API key prompt is hidden; flags are all optional)
clauda add botim --url https://openapi-glb.botim.me/api/llm-gw --auth token

# Run Claude Code on that endpoint
clauda botim                         # interactive session
clauda botim -p "explain this repo"  # one-shot; extra args pass through to claude

Commands

| Command | What it does | |---|---| | clauda <profile> [claude args...] | Launch claude with this profile's endpoint | | clauda add <name> [--url URL] [--key KEY] [--auth token\|apikey] [--model M] [--fast-model M] | Create a profile | | clauda list | List profiles | | clauda show <name> | Show a profile (key masked) | | clauda edit <name> | Open the profile file in $EDITOR | | clauda rm <name> | Delete a profile | | clauda env <name> | Print export lines, for eval "$(clauda env x)" |

Profiles

Profiles are plain KEY=VALUE files in ~/.config/clauda/profiles/<name>.env (created with mode 600), so you can also edit them by hand:

ANTHROPIC_BASE_URL=https://openapi-glb.botim.me/api/llm-gw
ANTHROPIC_AUTH_TOKEN=sk-...
ANTHROPIC_MODEL=claude-opus-4-7

Recognized keys:

| Key | Meaning | |---|---| | ANTHROPIC_BASE_URL | Required. The endpoint base URL | | ANTHROPIC_AUTH_TOKEN | Key sent as Authorization: Bearer ... (most proxies/providers) | | ANTHROPIC_API_KEY | Key sent as x-api-key: ... (official Anthropic API) | | ANTHROPIC_MODEL | Optional default model | | ANTHROPIC_SMALL_FAST_MODEL | Optional background/fast model | | API_TIMEOUT_MS | Optional request timeout | | anything else | Exported as-is to the claude process |

Environment variables

| Variable | Default | Meaning | |---|---|---| | CLAUDA_HOME | ~/.config/clauda | Where profiles and per-profile claude configs live | | CLAUDA_CLAUDE_BIN | claude | Path to the claude binary to launch |

How it works

clauda <profile> does exactly this, then execs claude:

  1. Scrubs any inherited ANTHROPIC_API_KEY / ANTHROPIC_AUTH_TOKEN / ANTHROPIC_BASE_URL from the environment.
  2. Exports every KEY=VALUE from the profile file.
  3. Sets CLAUDE_CONFIG_DIR=~/.config/clauda/claude-config/<profile> so the session is fully isolated from your ~/.claude subscription login.

Nothing is changed globally; close the session and plain claude is back to your subscription.

License

MIT