Feature request for product/service
Billing
Describe the request
I’d like to propose a token banking (rollover) feature for Cursor’s Pro subscription.
Many developers—especially entry‑level, independent, or part‑time users—experience uneven usage patterns. Some months involve little or no coding activity, while other months require intensive use. Under the current model, unused tokens from quieter months are lost, even though the subscription fee was paid in full.
When workload increases, users can quickly exhaust their monthly quota, despite having paid for multiple prior months where usage was minimal. This creates a sense of lost value and discourages consistent subscription use.
Why This Matters
- Developer workloads naturally fluctuate
- Cancelling and re‑subscribing month‑to‑month is disruptive
- Paying customers may feel penalised for periods of low usage
- The current system favours constant usage rather than long‑term loyalty
Proposed Improvement
- Introduce a token banking or rollover mechanism, where:
- Unused tokens from paid months carry forward
- Tokens can be used during higher‑demand periods
- Reasonable caps or expiry limits can prevent abuse
Benefits
- Fairer value for subscribers
- Better alignment with real‑world developer workflows
- Reduced frustration during high‑usage periods
- Increased long‑term subscription retention
This feature would significantly improve the Pro experience for users whose workloads vary month to month, while still maintaining predictable limits for the platform.
Thanks for considering this suggestion.
I think that would be nice!
Doesn’t have to be full credit, but maybe a percentage could rollover to the next month?
Also might have to consider if there should be a total cap (e.g. can’t rollover more than 3 total months - once you got 3 months banked you’re maxed out.)
Feature request for product/service
Billing
Describe the request
Recently upgraded-to-Ultra user here.
Upgrading to Ultra has required reducing other monthly expenses and, to be honest, did make me start looking around for more ‘affordable’ alternative approaches (be it local models or other providers etc, didn’t find any).
My subscription just renewed when I had only used 80% API usage, so am back to 1% usage (but didn’t use 20% of previous months quota).
Feature request to add:
- ‘Unused API usage banking’ (like ‘data banking’ for mobile phone plans)
This would go some way to avoiding overage in heavy usage months.
And it may make the Cursor offering more attractive to users who are starting to feel the pinch.
PS - For more context, I started using Opus 4.7 Extra-High and cant go back to anything else.
Feature request for product/service
Billing
Describe the request
On the $200/mo plan (Ultra), included usage (the $400 API budget + first-party models pool) fully resets every billing cycle and any unused amount is simply forfeited, even if you paid for the full month and only used half of it.
Feature request: allow unused included usage to roll over into the next billing cycle only (not indefinitely), and reset for good after that. This would make the plan feel much fairer for users whose usage varies month to month, without letting credits accumulate forever.
Right now it feels like we’re being charged for usage we paid for but never got to use, which is a pretty rough experience for a $200/mo subscription.