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

claudicle

v0.0.11

Published

CLI to install and run the Claudicle UI for Claude Code session telemetry

Readme

claudicle

npm version License: MIT

CLI to install and run the Claudicle UI — a self-hosted dashboard for Claude Code session telemetry (costs, tokens, tool usage, conversation transcripts).

Install

npm install -g claudicle

Requires Node.js >= 22.

Usage

Quick Setup

Run a single command to save credentials, initialize the ClickHouse schema, and install a system service:

# Set up the OTel Collector (receives telemetry from Claude Code)
claudicle setup collector --user claude --password claude

# Or set up the UI server (dashboard)
claudicle setup ui --user claude --password claude

All options from the individual commands (config init, init, install) are accepted.

Save ClickHouse connection parameters

claudicle config init --user claude --password claude

Options:

  • --clickhouse-url http://host:8123 — ClickHouse HTTP URL (default: http://localhost:8123)
  • --user / --password — ClickHouse credentials (required)
  • --database — ClickHouse database (default: claude_logs)
  • --port 3000 — UI port (default: 3000)

Initialize ClickHouse schema

claudicle init

Reads credentials from saved config. You can also pass --user and --password as overrides.

Start the UI

claudicle start

Options:

  • --port 3000 — UI port (default: 3000)
  • --clickhouse-url http://host:8123 — ClickHouse HTTP URL
  • --user / --password / --database — ClickHouse credentials

Stop the UI

claudicle stop

Check status

claudicle status

Update to latest version

claudicle update

Install OTel Collector as a system service

Downloads otelcol-contrib, generates a config with your ClickHouse credentials, and registers it as a systemd (Linux) or launchd (macOS) service with auto-restart.

claudicle install collector

Options:

  • --collector-version 0.115.0 — pin a specific collector version (default: latest)
  • --systemd / --launchd — force service type (default: auto-detect from OS)

Install UI as a system service

Registers the UI server as a systemd/launchd service so it starts on boot and auto-restarts.

claudicle install ui

Options:

  • --port 3000 — UI port (default: 3000)
  • --systemd / --launchd — force service type (default: auto-detect from OS)

How It Works

The CLI is a thin installer (~8 KB). On first claudicle start, it downloads a pre-built Next.js standalone bundle from GitHub Releases and caches it in ~/.claudicle/. The UI runs as a background Node.js process.

Configuration

Config is stored in env files (~/.claudicle/collector.env, ~/.claudicle/ui.env) and install metadata in ~/.claudicle/state.json. Override the config directory with the CLAUDICLE_HOME environment variable.

Full Documentation

For the complete setup with Docker Compose, OTel Collector, and JSONL log collection, see the main repository.

License

MIT