claude-usage-dashboard 1.5.0 → 1.5.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +6 -6
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -15,21 +15,21 @@ npx claude-usage-dashboard
15
15
 
16
16
  ## What You'll See
17
17
 
18
- ### See Every Machine in One Place
18
+ ### :computer: See Every Machine in One Place
19
19
 
20
20
  Use Claude on a laptop, a desktop, and a work machine? Most dashboards only see the one they're running on. This one syncs across all of them.
21
21
 
22
22
  Point it at any shared folder — Google Drive, Dropbox, OneDrive, a NAS, an rsync target — and every machine's logs roll up into one unified view. No server. No account. Just a folder you already have.
23
23
 
24
- ### Know What You're Spending
24
+ ### :dollar: Know What You're Spending
25
25
 
26
26
  Real-time projected API cost at your current usage rate — weekly and monthly. At 5% quota utilization, you might be burning through **$3,600/week** equivalent. The dashboard calculates this from your actual quota window, not estimates.
27
27
 
28
- ### Track Your Quota in Real Time
28
+ ### :bar_chart: Track Your Quota in Real Time
29
29
 
30
30
  Live utilization gauges for 5-hour, 7-day, and per-model quotas pulled directly from the Anthropic API. Auto-detects your plan tier (Pro / Max 5x / Max 20x). Never get throttled by surprise again.
31
31
 
32
- ### Track Your Quota Across Cycles
32
+ ### :chart_with_upwards_trend: Track Your Quota Across Cycles
33
33
 
34
34
  Anthropic doesn't publish exact token limits, and those limits can change without notice. The Quota Cycle History section gives you a running record of each 7-day cycle so you can see exactly how much you got and whether it stayed consistent.
35
35
 
@@ -37,11 +37,11 @@ For each cycle, the dashboard projects what your full token quota would be at 10
37
37
 
38
38
  That delta is the key signal: if your projected quota drops from one cycle to the next without you changing how you work, something changed on the platform side. Track your actual consumption week-over-week so you have real numbers when something feels off — not just a gut feeling. Up to 10 past cycles are retained across all your machines.
39
39
 
40
- ### Find What's Eating Your Tokens
40
+ ### :mag: Find What's Eating Your Tokens
41
41
 
42
42
  Per-project and per-session cost breakdowns show exactly where your usage goes. Sortable session table with cost, duration, and full token breakdown. Spot the expensive sessions instantly.
43
43
 
44
- ### Understand Your Cache Efficiency
44
+ ### :zap: Understand Your Cache Efficiency
45
45
 
46
46
  You'll probably discover that ~95% of your tokens are cache reads at 1/10th the cost. The dashboard visualizes cache read vs. cache write vs. uncached requests so you can see how efficiently Claude is using context.
47
47
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "claude-usage-dashboard",
3
- "version": "1.5.0",
3
+ "version": "1.5.1",
4
4
  "description": "Claude Code usage dashboard — token costs, quota cycle tracking, cache efficiency, multi-machine sync across all your devices",
5
5
  "main": "server/index.js",
6
6
  "bin": {