leolionart

CLIProxyAPI Dashboard — Data skill for Claude Code

Data community

The reporting system integrated into the CLIProxyAPI allows for monitoring usage and setting up alerts when data plan limits are reached.

How to install CLIProxyAPI Dashboard

This entry records only its repository, not the path inside it, so there is no exact command to give. Open leolionart/CLIProxyAPI-Dashboard and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What CLIProxyAPI Dashboard does

The reporting system integrated into the CLIProxyAPI allows for monitoring usage and setting up alerts when data plan limits are reached.

Alternatives in Data

  • Claude Code Usage Monitor — by Maciek-roboblog - A real-time terminal-based tool for monitoring Claude Code token usage 7k ★
  • Token Dashboard — See where Claude Code is burning tokens - turn raw JSONL transcripts into local cost analytics, hotspot views 669 ★
  • Dashboard Layout — Design and build a complete dashboard layout — sidebar navigation, KPI cards, chart areas, data tables, filter 309 ★

README

CLIProxy Dashboard

Real-time dashboard for monitoring CLIProxy usage, token consumption, estimated cost, and credential health.

CLIProxy Dashboard Preview

What this project includes

  • Collector (Python/Flask): polls CLIProxy Management API, computes deltas/costs, writes to PostgreSQL
  • Frontend (React + Nginx): charts and analytics UI
  • PostgreSQL: self-hosted DB initialized from init-db/schema.sql
  • PostgREST: read-only API layer for frontend
  • Skill tracker plugin distribution via marketplace + submodule (plugin/claude-skills-tracker)

Architecture

CLIProxy API / CPA-Manager Usage Service → Collector (Python) → PostgreSQL
Browser → Nginx:8417
          ├── /rest/v1/*       → PostgREST:3000 → PostgreSQL (read)
          └── /api/collector/* → collector:5001 (write/trigger)

Quick Start (run from this repository)

1) Prerequisites

  • Docker + Docker Compose v2
  • CLIProxy with remote management enabled

2) Configure CLIProxy Management API

Ensure your CLIProxy config includes:

remote-management:
  allow-remote: true
  secret: ""

For CLIProxyAPI v6.10+ / v7, usage statistics are served by an external usage service such as CPA-Manager. Keep the dashboard management URL pointed at CLIProxyAPI, and point the usage URL at the usage service:

usage-statistics-enabled: true
redis-usage-queue-retention-seconds: 3600

Quick verification:

curl -H "Authorization: Bearer " \
  http://localhost:18317/v0/management/usage

You should receive a JSON usage response. On older CLIProxyAPI versions that still expose `/v0/management/usage`, `CLIPROXY_URL` and `CLIPROXY_USAGE_URL` can be the same URL.

3) Clone and initialize submodule

git clone https://github.com/leolionart/CLIProxyAPI-Dashboard.git
cd CLIProxyAPI-Dashboard
git submodu