Back to DevLog

Feature Sprint: CC Dashboard v2 Gets Usage Stats, Context Fixes, and Headroom Tracking

3 min read

Just wrapped up a solid 1.5-hour feature sprint on CC Dashboard v2 and some AdminStack cleanup. The dashboard is really starting to feel like a proper monitoring tool now.

Major CC Dashboard Improvements

First up, I finally fixed the context window handling. Different Claude models have wildly different limits - Opus and Sonnet get a full 1M tokens while Haiku is stuck at 200K. The dashboard was hardcoded to 200K across the board, which was just wrong. Now it properly shows something like "14% (143.9K / 1.0M)" so you actually know where you stand.

The big addition is a full Usage Stats panel. This thing shows everything - tokens in/out, conversation turns, session counts - broken down by Today/This Week/This Month/All Time. But the real kicker is the cost tracking. It reads from a billing.json file (which hot-reloads without restarting) and shows actual billing vs what I'd pay for API usage. Current tally: $654 in actual bills vs $4,798 I would've paid OpenAI. That's $4,144 saved, or about 86% savings. Not bad!

I also added a "Needs Input" indicator that catches when Claude sends a tool use or question and then sits there waiting for 15-60 seconds. Just a pulsing amber badge, but it'll save me from those moments where I'm wondering why nothing's happening.

The Little Things That Matter

Relabeled "Cost" to "Max Value" everywhere since it's really showing API equivalent pricing for the Max plan. Added a Headroom proxy indicator in the header that shows active status plus real-time savings - currently showing 16.9% saved and about $24/month in avoided costs.

Session organization got way better too. There's now an Active/All filter toggle. Active view (the default) only shows sessions from the last 24 hours, with older stuff tucked away in a collapsible "Older Sessions" section.

AdminStack Cleanup

On the AdminStack side, I moved the CC Monitor out of the main Command Center navigation and tucked it into the Monitoring tab where it belongs. Also updated all the pricing references from Pro ($20/mo) to Max ($200/mo) since that's what I'm actually using now.

What's Next

There's a pile of uncommitted changes sitting in the cc-dashboard repo - 454 lines across multiple files. I need to clean up some debug screenshots and add proper .gitignore entries before committing. Might want to consider keeping billing.json out of version control if this ever goes public.

Thinking about adding daily/weekly cost trend charts next, maybe some historical tracking that persists beyond the current session data. Could even add a notification sound when something hits "needs input" state. But for now, this feels like a solid v2 foundation.

Share this post