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.