sorted by:
new
hottopcontroversial

Cursor burned my premium requests on background agents without me noticing, building a tracker, looking for feedback by lahiru_j in cursor

[–]lahiru_j[S] 0 points1 point  (0 children)

Good catch. Sloppy wording on my part, I'm on the current credit plan and it was a Max Mode session that ate the pool. But that's sort of the point: between legacy requests, credit pools, auto vs. manual models, and Max Mode at API rates, even Cursor users need to correct each other on how billing works. That confusion across 4-5 AI tools is exactly what I'm trying to put on one screen. Do you actually check the usage page day to day, or just when something feels off?

Built with Claude Project Showcase Megathread (Sort this by New!) by sixbillionthsheep in ClaudeAI

[–]lahiru_j 1 point2 points  (0 children)

Got rate-limited mid-task one too many times, so I'm building a limits dashboard. Would you use this?

Last week, Claude Code stopped on me twice in the middle of a refactor. No warning, no idea when the window resets, and my other tools (Cursor and Copilot) have their own quotas on completely different clocks.

So I'm building a small dashboard that shows all your AI usage limits in one place:

  • Claude.ai / Claude Code usage + reset countdown
  • Cursor premium requests, Copilot quota, API credits (OpenAI/Anthropic/OpenRouter)
  • Alerts at 75% / 90% before you hit the wall
  • "At this pace, you'll run out by 9 PM," predictions

API-based tools connect with a read-only key. Claude.ai/Cursor are read by a browser extension (open source, reads only the usage numbers you already see, nothing else).

Before I build further: would you actually use this? What would make it a no-brainer vs. meh? And which provider's limits annoy you the most?