Cursor's $20 Premium Plan | Users Slam Throttling Issues
A rising wave of dissatisfaction is sweeping through developers using Cursor's $20 Premium plan, with many claiming the service collapses under pressure after hitting its 500-request cap. Users have reported wait times stretching from 20 to 30 minutes per request, leading to urgent calls for solutions.
Developers in a Bind
As developers invest more time in Cursor for their projects, they face significant hurdles once the request limit is reached. "This is a major setback for my workflow," expressed one passionate user. With work piling up, the request throttling issue is becoming increasingly intolerable, forcing many developers to rethink their tool choices.
Community Insights and Strategies
Adjusting Usage Tactics
New insights from the community suggest that users are becoming savvy about their usage patterns. Some believe that overloading requests can exacerbate throttling problems. One comment noted, "The worse you spam the slow queue, the more you get throttled."
Switching Up Tools
Alternative tools are gaining traction as some developers explore options outside Cursor. One user pointed out the benefits of using Claude with MCP tools and suggested integrating these skills into VS Code along with a more affordable copilot plan. "Get the bulk of your work done in Claude and bounce over to VS Code as needed," they advised.
Mixed User Experiences
Interestingly, not all users report the same level of frustration. Some have expressed that their experience has not been significantly affected by throttling. A user based in Europe stated, "I was surprised how small of a difference it makes for me in the speed of the requests, almost as fast as premium," suggesting that regional factors might influence performance.
Growing Demand for Improvements
As developers advocate for better performance from their tools, many are also urging Cursor to step up its game. A common theme in the comments is a request for improved request handling capabilities. "There's a growing demand for Cursor to address these performance issues," emphasized several developers, who feel trapped by the limitations of the current service.
Key Findings
🚨 Users face severe wait times when exceeding request limits.
🔄 Suggestions for workaround include exploring alternative AI tools and adjusting account usage.
📈 Discussion around higher expectations for Cursor’s responsiveness is increasing.
With many developers depending on Cursor, addressing these performance frustrations is key. The ongoing conversation highlights the need for more flexible account management and tools adept at handling heavy workloads.
What's Next for Cursor?
With pressure mounting for improvements, it’s likely that Cursor will need to adapt to retain users. Experts point to a 60% chance that enhancements to request handling will be in place by mid-2025. If Cursor responds to user needs effectively, they could restore developer confidence and widen their user base, creating more reliable AI solutions in the process.
Parallels with Historical Constraints
The struggle developers face mirrors past experiences during crises that prompted innovation. Just as the energy crisis led to new transportation methods, the current throttling problems may push developers to rethink their strategies and toolsets. Are tech firms like Cursor ready to pivot under pressure?