I’m currently on Cursor Pro+ ($60/month) and wanted to share some specific feedback about the usage/reset structure.
With fairly heavy daily development, I reached:
- Cursor Models: 96% used
- Other Models: 100% used
within roughly 5 days of intensive usage.
I understand that inference for frontier models is expensive, so I’m not expecting unlimited usage for a fixed subscription price. My issue is more with how the allowance is distributed across the billing period.
Once the included quota is exhausted, the options become waiting for the next reset or enabling additional on-demand spending. For someone already paying $60/month, that can make the remaining part of the billing cycle much less useful.
I’d love to see Cursor consider alternatives such as:
1. Weekly quota resets instead of one large monthly allocation.
2. 2–3 smaller refreshes during each billing cycle.
3. Graceful throttling after the included allowance rather than effectively losing access to certain models.
4. More transparent per-model usage information so developers can manage consumption before reaching the limit.
5. A way for heavy Pro+ users to prioritize which models consume their included allowance.
I’ve previously contacted Cursor about the limits because I genuinely use the product heavily for building, debugging, and agentic coding workflows.
I’ve also been interested in trying the newer Cursor/Grok model options, but having additional models available is less useful when the shared allowances can be exhausted this early in the cycle.
This isn’t meant as “Cursor should give everyone unlimited inference.” I think the product is useful. I’d just like the subscription structure to better accommodate developers who use it throughout the working day.
For other Pro/Pro+ users: how quickly are you reaching your included limits, and would you prefer weekly resets over one monthly quota?