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

ccwatch-cli

v0.2.0

Published

A real-time terminal monitor for Claude Code sessions. Think `htop`, but for Claude Code.

Readme

ccwatch

A real-time terminal monitor for Claude Code sessions. Think htop, but for Claude Code.

It shows all your active Claude Code sessions in one place — what they're doing, how much they cost, and how much context they've used.

  ccwatch                                                     q: quit

  ● WORKING  ~/Code/my-project          Opus 4   $0.42   ctx:34% (68k)
              Read src/app.ts                                    12s ago

  ⏳ BLOCKED  ~/Code/other-project       Sonnet 4   $0.18   ctx:12% (24k)
              Permission requested                                3s ago

  ⌨ INPUT    ~/Code/side-project        Opus 4   $1.05   ctx:67% (134k)
              Waiting for input                                  45s ago

  ─────────────────────────────────────────────────────────────────
  3 sessions │ $1.65 total │ 1 blocked │ 1 awaiting input

Prerequisites

Install

# Build the binary
bun install
bun run build

# Put it on your PATH
cp ccwatch /usr/local/bin/

# Register hooks in Claude Code's settings
ccwatch install

ccwatch install adds hooks and a status line to ~/.claude/settings.json so that every Claude Code session reports its state.

Usage

Open a terminal and run:

ccwatch

Then use Claude Code in other terminals as usual. Sessions appear and update in real time.

Press q to quit.

How it works

Claude Code invokes ccwatch hook and ccwatch status as shell commands via its hooks/statusLine config. These write per-session JSON files to ~/.config/ccwatch/sessions/. The TUI watches that directory and re-renders on every change.

Subcommands

| Command | Purpose | |---|---| | ccwatch | Launch the TUI (default) | | ccwatch install | Register hooks and status line in ~/.claude/settings.json | | ccwatch hook | Receives hook events from Claude Code (not called directly) | | ccwatch status | Receives status line data from Claude Code (not called directly) |

Session states

| Icon | State | Meaning | |---|---|---| | | WORKING | Claude is actively processing | | | BLOCKED | Claude needs tool permission approval | | | INPUT | Waiting for your next prompt |

Status line

When installed, ccwatch status also outputs a formatted status line back to Claude Code showing model, project, git branch, context usage, and cost.

Development

bun run dev          # run directly (no compile step)
bunx tsc --noEmit    # type-check