Cursor Pro $20 Subscription Complaint: Usage Limit Reached After 5 Days
I purchased a Pro subscription to Cursor, an AI-powered IDE platform, for $20 per month so that I could develop my software projects without interruptions. Since this service is marketed as a monthly subscription, I expected to have continuous and reasonable access throughout the applicable billing period. However, I experienced serious problems within the very first week of my subscription.
Only 4–5 days after subscribing, while my project was at one of its most critical development stages, the system suddenly stopped working and displayed an “Other Models: 100% used” warning, effectively locking me out of further usage. Although I had already been charged upfront for 30 days of service, the available quota was exhausted after only a few days of normal development work, leaving me with no meaningful way to continue using the service. At that point, the system directed me either toward significantly more expensive plans such as the $60 Pro+ or $200 Ultra, or toward paying additional fees through “On-Demand” usage. Cursor’s current documentation confirms that the Pro plan has a monthly usage pool for “Other Models” and that additional usage can be purchased after the included allowance is exhausted.
In addition, even when I tried to continue by connecting my own external Google AI Studio API key, Cursor continued sending uncontrolled data requests in the background, causing the external API to reach its “Rate Limit” extremely quickly and rendering the development environment completely unusable. As a result, I was unable to make effective use of either the Pro subscription I had paid for or the external API access I had provided myself.
What I encountered does not feel like a genuine monthly subscription service. Instead, it appears to function as a system where the user pays an upfront $20 entry fee and can then find their project effectively blocked after only a few days because of limited or insufficient usage quotas, followed by pressure to make additional payments. I strongly object to this approach, which leaves users stranded in the middle of their development work and places them under pressure to spend more because of usage limits that I believe should be communicated much more clearly.
Despite the representation of the service as a monthly subscription, my access was effectively restricted from the fifth day onward. I therefore request that this service be treated as a defective service and that I receive a refund for the portion of the subscription period during which the promised service was not reasonably available to me. I also request that all software developers and programmers considering this platform be clearly informed about the risks associated with usage quotas and additional charges, and that Cursor revise its pricing and quota policies to make them more transparent, fair, and user-friendly.