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

clauder-hub

v0.1.33

Published

A local dashboard that runs, watches and automates the Claude Code sessions of every project on the machine

Readme


Features

Clauder Hub runs the real claude you already use, in real terminals, and adds what one terminal window cannot: every project at once, an inbox of everything Claude is waiting on, answers from your phone, scheduled runs and stats. Nothing is reimplemented and nothing is installed into Claude Code.

Also in the box:

  • The global page. A card per project with what is running, waiting and queued, plus one global bot that tags each message with its project (/projects, /use, /addproject).
  • Many sessions at once. A live panel of every project's sessions, terminals kept alive while you switch, and keys for the moves you repeat: Ctrl+K to jump anywhere, Alt+1..9 for the open sessions, Alt+W for the next one waiting on you, Ctrl+F to search a terminal, Ctrl+Enter to send now. Drop a file on a terminal to paste its path; select text to copy it.
  • Several Claude accounts. Add accounts on the global page, each with its own sign-in, and pick one for the hub, per project or per session. Skills, agents, plugins and settings stay shared.
  • Survives a restart. Sessions running when the hub stops (or crashes) are resumed when it starts again; queued runs go back on the queue.
  • Forms, or Claude. Jobs, runs, categories, presets and channels have forms; Set up with Claude hands the form to a Claude session instead, which carries on from what you filled in.
  • Variables. The env and headers Claude Code gets from .mcp.json, ~/.claude.json and the settings files, masked, with token expiry (JWTs, GitHub) and rotation written straight into the file after a confirm.
  • Where things stand. The project's git branch and changes at the foot of the sidebar, recent projects under its name, and on the global page each Claude account with its plan, its session and weekly usage (read from Claude Code's own /usage, no tokens spent) and today's tokens.
  • Settings. A global Settings page: the live panel, asking before a session is stopped, resuming after a restart.
  • Natural-language fallbacks. Misspell a command or describe a session ("the one fixing the login bug") and a small Haiku call offers its guesses as buttons. Nothing runs until you press one.
  • Prompts, memory and inventory. Edit every word the hub adds to a session, edit CLAUDE.md, rules, agents and skills after a diff, and see every agent, skill, command, MCP server, hook and plugin by scope.
  • MCP suggestions. A session blocked on a missing integration says so; claude mcp add --scope project runs only when you approve it.
  • Desktop notifications on Windows, macOS and Linux, and webhooks to Discord, Teams or your own endpoint.
  • Local only. The server listens on 127.0.0.1. Hooks are answered {} at once, so the hub can never approve or block a tool call by itself.

Install

Requirements: Node.js 22 or newer, and Claude Code installed and signed in (claude on your PATH).

npx clauder-hub .              # the current folder
npx clauder-hub ~/code/my-app  # or any project folder

Or keep it installed:

npm i -g clauder-hub
clauder-hub .

Open http://localhost:4329. If the port is taken the next free one is used (--port <n> picks one). The hub remembers its projects, so later runs can be just clauder-hub; running it again with another folder adds that folder to the hub already running. clauder-hub --help lists the options.

Data lives in ~/.clauder-hub (CLAUDER_HUB_HOME moves it): the project list, one database per project, and per-terminal settings files.


Developing

git clone https://github.com/goldyndevs/clauder-hub.git
cd clauder-hub
npm install
npm run dev -- /path/to/a/project   # server and web with reload

npm run typecheck and npm run build before a pull request. See CONTRIBUTING.md and CLAUDE.md for how the code is laid out and the rules it keeps.


FAQ

Does it replace Claude Code? No. It runs the claude you already have, with your login, settings and plugins, in a real terminal.

Does it write anything into my Claude Code setup? No. Hooks and the extra system prompt are passed per process with --settings and --append-system-prompt-file. The only exceptions are ones you ask for by name: a suggested claude mcp add --scope project, saving an instruction file after its diff, or rotating a value on the Variables page. An added Claude account gets a folder of its own under ~/.clauder-hub/profiles.

Do I need a public URL for Telegram or Slack? No. Telegram uses long polling and Slack uses Socket Mode, both outgoing connections.

What happens when I close the browser? Sessions keep running in the hub. Reopen the page and attach again.

And when I stop the hub? Its sessions stop with it, and come back by themselves the next time it starts (a switch on the global page turns that off). Their conversations are in Claude Code's transcripts either way.

Can it see sessions I started in a normal terminal? Yes, with their stats. Resume one in the hub to answer it from the inbox or a channel.

Does it cost extra tokens? Stats and /summary are read from transcripts. Only the natural-language fallbacks in channels make a small Haiku call.


License

MIT © goldyndevs