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

nvicode

v0.1.20

Published

Route Claude Code, Codex CLI, and OpenClaw through NVIDIA or OpenRouter with one setup.

Readme

Nvicode - Free unlimited claudecode 40RPM

CI npm version package node >=20 license: MIT

Route Claude Code, Codex CLI, and OpenClaw through NVIDIA or OpenRouter with one setup.

nvicode lets you choose a provider once, save the API key once, pick a model once, and then launch the coding tool you want against that same backend.

What it gives you:

  • One guided setup flow for provider, key, and model
  • Claude Code support
  • Codex CLI support
  • OpenClaw support
  • NVIDIA proxy mode with pacing and local usage tracking
  • OpenRouter direct mode for compatible models
  • Dynamic NVIDIA model discovery for current Kimi, DeepSeek, GLM, and Qwen picks

Supported environments:

  • macOS
  • Ubuntu/Linux
  • WSL
  • Native Windows with Claude Code installed and working from PowerShell, CMD, or Git Bash

Quickstart

Install nvicode:

npm install -g nvicode

Choose provider, key, and model:

nvicode select model

Launch the tool you want:

nvicode launch claude
nvicode launch codex
nvicode launch openclaw

Provider setup:

What happens after first launch:

  • The first successful nvicode launch claude installs persistent plain claude routing.
  • The first successful nvicode launch codex installs persistent plain codex routing.
  • nvicode launch openclaw updates the default OpenClaw profile for the selected provider/model.

After that, plain:

claude
codex

continues using your selected nvicode provider and model.

Screenshots

Save your API key

nvicode auth

Choose a model

nvicode select model

Launch through your selected provider

nvicode launch claude

How It Works

  • Claude Code:
    • NVIDIA uses a local Anthropic-compatible proxy on 127.0.0.1:8788
    • OpenRouter connects directly to https://openrouter.ai/api
  • Codex CLI:
    • uses the local nvicode proxy
    • nvicode configures Codex to talk to that proxy through the Responses API
  • OpenClaw:
    • updates the default OpenClaw config for the selected provider/model
    • restart the gateway after config changes:
openclaw gateway restart

Commands

Common commands:

nvicode select model
nvicode launch claude
nvicode launch codex
nvicode launch openclaw
nvicode dashboard
nvicode usage
nvicode activity
nvicode models
nvicode config
nvicode auth
nvicode launch claude -p "Reply with exactly OK"
nvicode launch codex "Explain this project"

Behavior notes:

  • nvicode select model asks for provider, optional API key update, and model choice in one guided flow.
  • For NVIDIA, model selection fetches the live NVIDIA catalog and highlights one current top pick each from Kimi, DeepSeek, GLM, and Qwen before falling back to curated defaults.
  • Claude Code uses direct OpenRouter mode for OpenRouter, and proxy mode for NVIDIA.
  • Codex currently uses the local nvicode proxy path.
  • nvicode usage, activity, and dashboard are currently focused on NVIDIA proxy sessions.
  • OpenRouter does not currently produce the same local usage visibility as the NVIDIA proxy flow.
  • NVIDIA requests are paced to 40 RPM by default. Override with NVICODE_MAX_RPM if your account allows more.

In an interactive terminal, nvicode usage refreshes live every 2 seconds. When piped or redirected, it prints a single snapshot.

The usage dashboard compares your local NVIDIA run cost against Claude Opus 4.6 at $5 / MTok input and $25 / MTok output, based on Anthropic pricing as of 2026-03-30. If your NVIDIA endpoint is not free, override local cost estimates with NVICODE_INPUT_USD_PER_MTOK and NVICODE_OUTPUT_USD_PER_MTOK.

Requirements

  • Claude Code must already be installed to use nvicode launch claude.
  • Codex must already be installed to use nvicode launch codex. Install with npm install -g @openai/codex.
  • OpenClaw must already be installed to use nvicode launch openclaw. Install with npm install -g openclaw@latest.
  • Node.js 20 or newer is required to install nvicode.
  • OpenClaw itself requires Node.js >=22.14.0.
  • On native Windows, Claude Code itself requires Git for Windows. See the Claude Code setup docs.

Local Development

These steps are only for contributors working from a git checkout. End users do not need them.

npm install
npm run build
npm link

Notes

  • thinking is disabled by default because some NVIDIA reasoning models can consume the entire output budget and return no visible answer to Claude Code.
  • The proxy supports basic text, tool calls, tool results, and token count estimation.
  • The proxy includes upstream request pacing and retries on NVIDIA 429 responses.
  • Claude Code, Codex CLI, and OpenClaw remain the frontends; the selected provider/model becomes the backend.