Launched this week
CUStats
Never hit limit unexpectedly again - on macOS, iOS, Android
49 followers
Never hit limit unexpectedly again - on macOS, iOS, Android
49 followers
Stop wondering if you're about to hit your AI limit. Just glance at your menubar or phone. CUStats monitors Claude & OpenAI Codex usage in real-time: - macOS menubar + iOS/Android apps - Multi-account support (Claude + Codex) - Pace prediction to forecast weekly usage - 5-hour, 7-day, and model-specific limits - Historical views with GitHub-style charts - Trigger to start a fresh session - Privacy first GIVEAWAY: 20 FREE codes! Upvote + comment so I can DM you!
Hey ProductHunt!
I'm the solo developer behind CUStats, and I built this because I kept running into the same frustrating problem: I'd be deep in a coding session with Claude Code or Codex, finally in the zone, and suddenly... rate limited.
The worst part wasn't the limit itself - it was the uncertainty. "How close am I?" "Should I save this conversation for something more important?" That mental overhead was killing my flow.
CUStats puts your usage right where you need it:
- macOS: In your menubar - always visible + Detail Dashboard
- iOS/Android: On your phone - check anytime
A quick glance tells you everything:
- Green = plenty of headroom
- Orange = approach with caution
- Red = time to wrap up
When you hit 100%, you get a live countdown showing exactly when you can continue.
Few import features (among many):
Support both Claude Code and OpenAI Codex
Support multiple accounts: Have work and personal accounts? Track up to 5 accounts simultaneously. The All Accounts Dashboard on macOS shows everything at a glance.
Pace Prediction: This is my favorite feature. It projects your end-of-week usage and tells you if you're on track (Healthy), getting close (Risky), or going to exceed (Over). No more guessing.
Cross-Platform: CUStats is now available on macOS, iOS, with Android coming soon. Same great experience on every device.
Trigger to start a fresh session: start a new session at 7am everyday (even when you are sleeping), support multiple trigger.
Privacy first: all data store locally
And many more.
---
GIVEAWAY: I'm giving away 20 FREE redeem codes!
To enter:
1. Upvote this post
2. Comment below so that I can DM you
I'll randomly pick 20 winners and DM the codes within 48 hours!
---
Would love to hear your feedback! What other metrics would be useful to track? Any feature requests? I'm here to answer questions all day.
Thanks for checking out CUStats!
@luongnv89 Nice bro. Anw, what can we do after knowing that we'll hit quota limit soon? If you still have to rely on AI, you can't stop using it even if you know you'll hit it soon. So how can it solve the issue?
When i use AI agent like Claude Code, i've felt a bit scared because of hitting limit of usage.
You've solved that. Great!
@highlightyourproduct What can you do after knowing that you'll hit quota limit? If you still have to rely on AI, you can't stop using it even if you know you'll hit it soon. So how it can solve the issue?
@highlightyourproduct @hector_ta_1989 Knowing your patterns and your limits helps you plan better when using Claude or Codex.
From my experience, I set a trigger to start a fresh session at 6 a.m. before I have even opened my laptop. Then I start working at 8 a.m. After my morning routine with emails and other tasks, I start my coding session at 9 a.m. At this moment, I have two hours at full capacity to spin up many sessions at the same time. At 11 a.m., I have a fresh new session at 100%, so I can continue with my intensive coding flow.
I have a Max 5x plan, which usually keeps me going for about two to two and a half hours with my usual workflow. By planning like this, I can have around four to five hours of 200% usage.
In other cases, when you know you are going to hit the limit, you can prioritize which session to continue and which session to pause.
Especially with the pace of weekly usage, I can adjust my speed to ensure I never hit the limit before the end of the week.
Overall, knowing your usage stats and patterns helps you better plan for maintaining momentum, increasing productivity, and, especially, gaining peace of mind.
Token is the new currency, monitor your usage limit is quite similar with monitor your wallet :D
@luongnv89 Oh, your routine is so helpful. Brilliant!
1Page
Nice!
@pooran_prasad_rajanna Thanks
Cloudthread
Very cool! How does it differentiate between Personal and Work token consumption?
@daniele_packard Hi, they are just the alias name, you can name them as you wish
The "flow state interrupted by rate limit" problem is painfully real, especially with Claude Code where you're deep in a debugging session and suddenly hit a wall. Pace prediction is brilliant - knowing whether you'll hit the weekly limit before Friday changes how you allocate usage across projects. The green/orange/red visual system makes it easy to check status at a glance without context-switching. Multi-account support for work/personal tracking is essential. Does the pace prediction account for usage patterns like weekday vs weekend activity, or is it a simple linear projection?
@easytoolsdev Thanks, for now it is a simple linear projection. There is a much more complicated calculation based on actual usage of user, but at the end it is just a point of view. So I take it as that simple for now.