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

@yashau/dexuse

v2026.6.2801

Published

Fancy terminal usage explorer for Codex, Hermes, and OpenClaw token history

Readme

dexuse

OpenAI / Codex token usage, finally visible.

dexuse turns local OpenAI/Codex-style usage history into a polished terminal dashboard with timelines, model splits, source breakdowns, cache reads, reasoning tokens, Codex quota badges, reset-credit markers, and JSON export.

Rust TUI npx

Why it exists

OpenAI/Codex tools leave token history scattered around your machine. dexuse pulls the useful parts into one beautiful local view so you can answer:

  • Which model burned the most tokens?
  • How much was cached instead of fresh input?
  • Did it come from Codex, Hermes, or OpenClaw?
  • What changed by day, week, month, or year?
  • How much Codex quota is left in the 5-hour and 7-day windows?
  • When do banked Codex reset credits expire?
  • Can I get the same totals as JSON? Yep.

No cloud account. No upload. It reads local files only.

One-liner

npx @yashau/dexuse

From a checkout:

mise install
mise run bundle
pnpm run dexuse

mise is the primary repo tool: it installs the pinned Rust/Node toolchains and owns the repeatable local tasks for formatting, tests, builds, screenshots, package checks, and release-binary bundling. Use the direct cargo/pnpm commands below only as lower-level fallbacks.

Handy moves

npx @yashau/dexuse
npx @yashau/dexuse --json
npx @yashau/dexuse --json --from 2026-06-01 --to 2026-06-06 --granularity day
npx @yashau/dexuse --codex-only
npx @yashau/dexuse --hermes-only
npx @yashau/dexuse --openclaw-only

dexuse automatically looks in the usual places:

  • Codex: ~/.codex, including archived sessions
  • Hermes: ~/.hermes, %LOCALAPPDATA%\hermes, and profile databases
  • OpenClaw: ~/.openclaw, with legacy ~/.clawdbot fallback

Need a custom path?

npx @yashau/dexuse --codex-home ~/.codex
npx @yashau/dexuse --hermes-home ~/.hermes
npx @yashau/dexuse --openclaw-home ~/.openclaw

Screenshots

Drill into time

Compare models

See where the tokens came from

Keyboard moves

  • 1 / 2 / 3: Timeline, Models, Sources
  • Tab, Shift+Tab, [ / ]: switch tabs
  • / or h / l: move the selected period
  • Enter / Space: drill down through time
  • u / Backspace: go back up
  • y / m / w / d: year, month, week, day
  • q / Esc: quit

What it counts

dexuse keeps the buckets separate so big cached sessions do not look like fresh input:

  • input tokens
  • cached input tokens
  • cache write tokens
  • output tokens
  • reasoning tokens
  • API calls
  • estimated cost when the source provides it

JSON output includes totals, time buckets, model splits, provider splits, source splits, codex_quota, and codex_reset_credits when quota probing is available.

Built for more OpenAI/Codex sources

Codex, Hermes, and OpenClaw are harnesses over local OpenAI/Codex-style usage logs. The ingestion layer is modular, so another compatible local agent can be added without turning main.rs into spaghetti. Maintainer details live in AGENTS.md.

Ship it locally

Use mise for setup and quality gates:

mise install
mise run check
mise run screenshots
mise run pack

Direct commands work too when you need to debug a single underlying step:

cargo fmt --check
cargo test
cargo clippy --all-targets --all-features -- -D warnings
cargo build --release
python scripts/bundle_current.py
python scripts/smoke_json.py
pnpm run screenshots
pnpm pack --dry-run

License

MIT.