Hey, thanks for the report.
Opus 4.5 can burn through usage faster than other models, but that isn’t a bug. Usage is calculated from tokens at the model’s API rates, not from a fixed number of “requests”. Opus is more expensive on the API, so limits get used up faster.
A few important things to check:
-
Make sure MAX Mode wasn’t enabled by accident. The MAX Mode button is very close to the Opus model picker, so it’s easy to click it by mistake. Other users mentioned this here:
Cursor’s Undisclosed Model Upgrade Issue -
Check the detailed breakdown. Go to https://cursor.com/dashboard?tab=usage and review the per-request token breakdown (input/output/cache). That should also make it clear whether MAX Mode was used.
-
How the counting works. I explained it in more detail here:
Opus 4.5 Doesn't Show Requests Count as 2x Requests - #5 by deanrie -
Official docs:
- Models and pricing: Models | Cursor Docs
- Plans: Pricing | Cursor Docs
If, after checking the dashboard, you’re sure MAX Mode wasn’t used but usage still looks abnormally high, please share:
- A screenshot of the usage breakdown from the dashboard
- Request IDs for a few affected requests (in chat: top-right menu → Copy Request ID)
- Rough context size, like how many files were attached and the approximate repo size
Let me know what the dashboard shows.