# Why not bring back the old 500-request system for the Pro version? **URL:** \ **Category:** Feedback\ **Created:** [May 22, 2026, 11:41pm UTC](https://forum.cursor.com/t/why-not-bring-back-the-old-500-request-system-for-the-pro-version/161362 "2026-05-22T23:41:16Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [May 23, 2026, 11:02am UTC](https://forum.cursor.com/t/why-not-bring-back-the-old-500-request-system-for-the-pro-version/161362/6 "2026-05-23T11:02:53Z")
Hey, thanks for the feedback. To be candid, we’re not planning to bring back the old 500 requests/month plan. Moving to token-based pricing was a deliberate decision, and we won’t be rolling it back. I get that for new users this can feel abrupt, especially when you hit spend quickly. A few practical things that can help reduce usage: - Spend limits: you can set a hard monthly limit so there are no surprises [Spend limits | Cursor Docs](https://cursor.com/help/account-and-billing/spend-limits) - Model choice: different models burn tokens very differently. For simple tasks, the faster models are usually enough. MAX/Opus is best saved for when you really need it [Models & Pricing | Cursor Docs](https://cursor.com/docs/models-and-pricing) - Context management: the fewer irrelevant files in context, the cheaper the request. .cursorignore and targeted @ mentions help a lot. Related threads where users share how they optimized usage: - [Cursor is expensive](https://forum.cursor.com/t/126446) - [The New Pricing System is Insane – A Main Reason I’ll Switch Platforms](https://forum.cursor.com/t/135489) If you’re seeing specific requests that are eating an unreasonable number of tokens, send the Request ID and we’ll take a look at what’s going on. --- _[View the full topic](https://forum.cursor.com/t/why-not-bring-back-the-old-500-request-system-for-the-pro-version/161362)._