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

@dong-/cdxx

v0.1.0

Published

Multi-profile wrapper and live quota failover for Codex CLI

Readme

cdxx

cdxx is a small Codex CLI companion inspired by agyx.

It provides:

  • local Codex auth profile save/use/next
  • passive quota scanning from $CODEX_HOME/sessions
  • optional shell integration so codex runs through cdxx session
  • live autoswitch and codex resume <session_id> failover when a profile reaches quota

Install locally

cd ~/codexx
npm link
cdxx install
source ~/.zshrc

For the current terminal only:

eval "$(cdxx shell-init)"

Profile workflow

Save the currently active Codex login:

cdxx save personal

Add another profile:

cdxx login work

Switch profiles:

cdxx list
cdxx use personal
cdxx next
cdxx current

cdxx stores profile credentials under ~/.config/cdxx/profiles/<name>/auth.json with owner-only permissions. The active Codex credential remains $CODEX_HOME/auth.json, normally ~/.codex/auth.json.

Quota workflow

Scan local Codex session transcripts:

cdxx scan
cdxx scan --json
cdxx scan --json --full

Run Codex through the wrapper:

cdxx session -- "inspect this repo"

After a wrapped session exits, cdxx scans new or modified Codex transcripts and records rate-limit status on the active profile. Enable live profile failover:

cdxx autoswitch on

With autoswitch enabled, the wrapper tails the matched Codex transcript by byte offset. If Codex reports an exhausted rate limit, cdxx terminates the current Codex process, switches to the next available saved profile, and starts codex resume <session_id> from the same working directory.

Session matching

Codex does not expose an agy --log-file style TUI transcript path option. cdxx matches the child session from Codex's real transcript files instead:

  1. Snapshot $CODEX_HOME/sessions/**/*.jsonl immediately before launching Codex.
  2. Poll new or modified JSONL files while Codex runs.
  3. Read only the first session_meta record and match: payload.cwd == process.cwd(), payload.originator == "codex-tui", and payload.timestamp >= launchTime - 5s.
  4. Tail the matched JSONL file from the pre-launch file size, so runtime quota checks depend only on newly appended log bytes.

The matched payload.session_id/payload.id is suitable for codex resume.

Notes

  • cdxx reads Codex JSONL transcripts but does not print prompts or responses.
  • A profile is treated as exhausted when Codex reports primary.used_percent >= 100, secondary.used_percent >= 100, or a non-null rate_limit_reached_type.
  • Reset times are derived from the resets_at epoch fields stored by Codex.