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

theclawbay

v0.2.13

Published

The Claw Bay CLI: one-time API-key setup for direct Codex access, with optional relay fallback.

Readme

The Claw Bay (theclawbay)

theclawbay is a customer CLI for The Claw Bay.

This package no longer runs local account login automation or local account switching flows.

Not affiliated with OpenAI or Codex. Not an official tool.

Requirements

  • Node.js 18+
  • Codex CLI (@openai/codex) and/or OpenClaw CLI

Install

npm i -g theclawbay

If you use nvm, keep a single global prefix to avoid duplicate binaries:

npm config delete prefix

One-Time Setup (Recommended)

Use your purchased API key from your dashboard:

theclawbay setup --api-key <apiKey>

This auto-detects installed clients and writes direct WAN API-key config so users can run directly. It configures Codex with model_provider = "theclawbay" and a managed bearer token, auto-selects the highest backend-advertised model, and preserves conversation visibility by neutralizing legacy local session provider tags so chats remain visible across provider modes.

It also configures OpenClaw/OpenCode automatically when those CLIs are installed. OpenClaw/OpenCode provider configs are written with a literal API key (no env var dependency). If OpenClaw has a stale ${CODEX_LB_API_KEY} placeholder from an older setup, theclawbay setup now auto-heals ~/.openclaw/openclaw.json.

CODEX_LB_API_KEY is persisted for restarts in:

  • ~/.config/theclawbay/env
  • ~/.bashrc
  • ~/.zshrc
  • ~/.profile
  • ~/.vscode-server/server-env-setup (and ~/.vscode-server-insiders/server-env-setup when present)

If you operate a custom backend, pass it explicitly:

theclawbay setup --api-key <apiKey> --backend https://your-domain.com

After setup, restart terminal/VS Code once only if your own shell workflows depend on CODEX_LB_API_KEY.

Codex Extension Behavior

  • In API-key provider mode, Codex may label the model source as Custom.
  • Full ChatGPT account model-picker behavior is tied to ChatGPT auth mode.
  • theclawbay setup keeps your existing Codex login state unchanged on purpose (so local history context is preserved and setup stays non-destructive).

Run Relay (Optional)

Only needed as a fallback compatibility mode:

theclawbay link --api-key <apiKey>
theclawbay proxy

By default this starts a local relay on http://127.0.0.1:2455 and forwards to:

  • https://theclawbay.com/api/codex-auth/v1/proxy/...

The command auto-detects whether openclaw and/or opencode are installed and configures them automatically.

Notes

  • End users only need API keys. They do not need upstream account credentials.
  • Keep your backend on HTTPS for WAN usage.
  • Linked config is stored at ~/.codex/theclawbay.managed.json.