(One intermediate revision by one other user not shown)
Line 17:
Line 17:
After introducing an Unlimited Pro plan, a hidden Pro+ upgrade, and higher-priced Ultra Plan in mid-June 2025<ref>{{Cite web |title=Clarifying June 16 Pro Changes |url=https://forum.cursor.com/t/clarifying-june-16-pro-changes/111740 |access-date=2025-07-05 |url-status=live |archive-url=http://web.archive.org/web/20251217052720/https://forum.cursor.com/t/clarifying-june-16-pro-changes/111740 |archive-date=17 Dec 2025}}</ref>, shortly after Cursor quietly changed the Pro plan description from ''"Unlimited Agent Requests" to "Unlimited Agent Requests *Usage Limits Apply for some models"'' and again early July to ''"Extended limits on agent"'' without clarifying actual limits or notifying existing customers. The company implemented a system based on "$20+ of model inference" allowance but provided no tools for users to track consumption against this limit.<ref>{{Cite web |title=Cursor Community Discussion: No Usage Tracking |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/18 |access-date=2025-07-05 |url-status=live |archive-url=http://web.archive.org/web/20250710051320/https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028 |archive-date=10 Jul 2025}}</ref>
After introducing an Unlimited Pro plan, a hidden Pro+ upgrade, and higher-priced Ultra Plan in mid-June 2025<ref>{{Cite web |title=Clarifying June 16 Pro Changes |url=https://forum.cursor.com/t/clarifying-june-16-pro-changes/111740 |access-date=2025-07-05 |url-status=live |archive-url=http://web.archive.org/web/20251217052720/https://forum.cursor.com/t/clarifying-june-16-pro-changes/111740 |archive-date=17 Dec 2025}}</ref>, shortly after Cursor quietly changed the Pro plan description from ''"Unlimited Agent Requests" to "Unlimited Agent Requests *Usage Limits Apply for some models"'' and again early July to ''"Extended limits on agent"'' without clarifying actual limits or notifying existing customers. The company implemented a system based on "$20+ of model inference" allowance but provided no tools for users to track consumption against this limit.<ref>{{Cite web |title=Cursor Community Discussion: No Usage Tracking |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/18 |access-date=2025-07-05 |url-status=live |archive-url=http://web.archive.org/web/20250710051320/https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028 |archive-date=10 Jul 2025}}</ref>
[[File:Initial Unlimited Pricing.png|thumb|200x200px|A screenshot of the initial description of the Pro plan]]
==Service Degradation and Consumer Exploitation==
==Service Degradation and Consumer Exploitation==
Line 29:
Line 29:
*Changed "Unlimited Agent Requests" to "Extended limits on agent" on pricing page
*Changed "Unlimited Agent Requests" to "Extended limits on agent" on pricing page
*Implemented usage limits based on vague ''"$20+ of model inference"'' allowance
*Implemented usage limits based on vague ''"$20+ of model inference"'' allowance
*Introduced harsh rate limiting with reset periods described only as ''"5-24 hours"''<ref>{{Cite web |title=Cursor Documentation on Rate Limits |url=https://docs.cursor.com/rate-limits |access-date=2025-07-05 |url-status=live |archive-url=https://web.archive.org/web/20260216025928/https://cursor.com/docs |archive-date=16 Feb 2026}}</ref>[[File:Updated Unlimited Pricing.png|thumb|200x200px]][[File:July 03, 2025, Updated Pricing.png|thumb|223x223px]]
*Introduced harsh rate limiting with reset periods described only as ''"5-24 hours"''<ref>{{Cite web |title=Cursor Documentation on Rate Limits |url=https://docs.cursor.com/rate-limits |access-date=2025-07-05 |url-status=live |archive-url=https://web.archive.org/web/20260216025928/https://cursor.com/docs |archive-date=16 Feb 2026}}</ref>[[File:Updated Unlimited Pricing.png|thumb|200x200px|A screenshot of the description of the Pro-plan showing a hidden disclaimer near the "Unlimited agent requests" line]][[File:July 03, 2025, Updated Pricing.png|thumb|223x223px|A screenshot showing the description of the Pro tier as of 3 July 2025. Notice how the first line was modified to "Extended limits on agent"]]
*Removed transparency features that would allow users to track usage against limits<ref>{{Cite web |title=User Complaints About Lack of Usage Dashboard |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/20 |access-date=2025-07-05 |url-status=live |archive-url=http://web.archive.org/web/20250710051320/https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028 |archive-date=10 Jul 2025}}</ref>
*Removed transparency features that would allow users to track usage against limits<ref>{{Cite web |title=User Complaints About Lack of Usage Dashboard |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/20 |access-date=2025-07-05 |url-status=live |archive-url=http://web.archive.org/web/20250710051320/https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028 |archive-date=10 Jul 2025}}</ref>
Line 78:
Line 78:
*A detailed 51-page forum thread documented user experiences with screenshots, usage data, and technical analysis<ref>{{Cite web |title=Pro Plan Rate Limit Transparency Issues - Cursor Forum |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028 |access-date=2025-07-05 |url-status=live |archive-url=http://web.archive.org/web/20250710051320/https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028 |archive-date=10 Jul 2025}}</ref>
*A detailed 51-page forum thread documented user experiences with screenshots, usage data, and technical analysis<ref>{{Cite web |title=Pro Plan Rate Limit Transparency Issues - Cursor Forum |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028 |access-date=2025-07-05 |url-status=live |archive-url=http://web.archive.org/web/20250710051320/https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028 |archive-date=10 Jul 2025}}</ref>
*[[File:X post on cursorai.jpg|thumb|twitter post from disgruntled customer of cursorai]]Hundreds of complaints across Twitter/X from developers worldwide experiencing identical issues<ref>{{Cite web |title=Developer Complaints on Twitter |url=https://x.com/0ni_x4/status/1940885976127283342 |access-date=2025-07-05}}</ref>
*[[File:X post on cursorai.jpg|thumb|twitter post from disgruntled customer of cursorai]]Hundreds of complaints across Twitter/X from developers worldwide experiencing identical issues<ref>{{Cite web |title=Developer Complaints on Twitter |url=https://x.com/0ni_x4/status/1940885976127283342 |access-date=2025-07-05 |archive-url=http://web.archive.org/web/20250723220606/https://x.com/0ni_x4/status/1940885976127283342 |archive-date=23 Jul 2025}}</ref>
*Community-maintained archives created due to forum censorship and thread hiding<ref>{{Cite web |title=Archive of Hidden Threads |url=https://archive.is/QDnSS |access-date=2025-07-05}}</ref>
*Community-maintained archives created due to forum censorship and thread hiding<ref>{{Cite web |title=Archive of Hidden Threads |url=https://archive.is/QDnSS |access-date=2025-07-05}}</ref>
*Reddit discussions confirming the same problems across the user base<ref>{{Cite web |title=Reddit User Reports on Cursor Rate Limits |url=https://www.reddit.com/r/cursor/comments/1lqvl21/cursor_12_and_claude_4_sonnet_rate_limit_is_this/ |access-date=2025-07-05}}</ref>
*Reddit discussions confirming the same problems across the user base<ref>{{Cite web |title=Reddit User Reports on Cursor Rate Limits |url=https://www.reddit.com/r/cursor/comments/1lqvl21/cursor_12_and_claude_4_sonnet_rate_limit_is_this/ |access-date=2025-07-05 |archive-url=https://web.archive.org/web/20260223035255/https://old.reddit.com/r/cursor/comments/1lqvl21/cursor_12_and_claude_4_sonnet_rate_limit_is_this/ |archive-date=23 Feb 2026}}</ref>
===User Actions===
===User Actions===
Latest revision as of 18:02, 14 March 2026
⚠️Article status notice: This article has been marked as incomplete
This article needs additional work for its sourcing and verifiability to meet the wiki's Content Guidelines and be in line with our Mission Statement for comprehensive coverage of consumer protection issues.
This notice will be removed once sufficient documentation has been added to establish the systemic nature of these issues. Once you believe the article is ready to have its notice removed, please visit the Moderator's noticeboard, or the discord and post to the #appeals channel.
Learn more ▼
This Article Requires Additional Verification
This article has been flagged due to verification concerns. While the topic might have merit, the claims presented lack citations that live up to our standards, or rely on sources that are questionable or unverifiable by our standards. Articles must meet the Moderator Guidelines and Mission statement; factual accuracy and systemic relevance are required for inclusion here!
Why This Article Is In Question
Articles in this wiki are required to:
Provide verifiable & credible evidence to substantiate claims.
Avoid relying on anecdotal, unsourced, or suspicious citations that lack legitimacy.
Make sure that all claims are backed by reliable documentation or reporting from reputable sources.
Examples of issues that trigger this notice:
A topic that heavily relies on forum posts, personal blogs, or other unverifiable sources.
Unsupported claims with no evidence or citations to back them up.
Citations to disreputable sources, like non-expert blogs or sites known for spreading misinformation.
How You Can Improve This Article
To address verification concerns:
Replace or supplement weak citations with credible, verifiable sources.
Make sure that claims are backed by reputable reporting or independent documentation.
Provide additional evidence to demonstrate systemic relevance and factual accuracy. For example:
Avoid: Claims based entirely on personal anecdotes or hearsay without supporting documentation.
Include: Corporate policies, internal communications, receipts, repair logs, verifiable video evidence, or credible investigative reports.
If you believe this notice has been placed in error, or once the article has been updated to address these concerns, please visit the Moderator's noticeboard, or the #appeals channel on our Discord server: Join here.
Cursor AI silently changed their "unlimited" Pro plan to severely rate-limited without notice, locking users out after 3-7 requests & forcing them to upgrade to regain functionality.[1]
Cursor AI, a developer-focused AI code assistant, marketed its $20/month Pro plan with "Unlimited Agent Requests,"[2] targeting professional developers who depend on advanced models like Anthropic Claude 4 Sonnet for coding workflows. The service was sold as a premium development tool that provides reliable access to frontier AI models for professional software development.
After introducing an Unlimited Pro plan, a hidden Pro+ upgrade, and higher-priced Ultra Plan in mid-June 2025[3], shortly after Cursor quietly changed the Pro plan description from "Unlimited Agent Requests" to "Unlimited Agent Requests *Usage Limits Apply for some models" and again early July to "Extended limits on agent" without clarifying actual limits or notifying existing customers. The company implemented a system based on "$20+ of model inference" allowance but provided no tools for users to track consumption against this limit.[4]
A screenshot of the initial description of the Pro plan
Days after June 16, 2025, launch, Cursor quietly walked back "Unlimited Agent Requests"
Added on asterisks to the unlimited messaging "Unlimited Agent Requests *Usage Limits Apply for some models"
On June 16, 2025, Cursor AI pushed through large changes to their Pro Plan terms without properly notifying customers:[5]
Changed "Unlimited Agent Requests" to "Extended limits on agent" on pricing page
Implemented usage limits based on vague "$20+ of model inference" allowance
Introduced harsh rate limiting with reset periods described only as "5-24 hours"[6]A screenshot of the description of the Pro-plan showing a hidden disclaimer near the "Unlimited agent requests" lineA screenshot showing the description of the Pro tier as of 3 July 2025. Notice how the first line was modified to "Extended limits on agent"
Removed transparency features that would allow users to track usage against limits[7]
Even after the official response, fundamental issues remained unresolved:
Users continued experiencing rate limiting after just 3 prompts despite documentation claiming 225 requests/month
Reset timing described vaguely as "5-24 hours" with no guarantees ("best-effort basis")
No real-time usage tracking implementation to help users manage consumption
Forum user doing math to demonstrate how cursor is 29x worse than claudeValue proposition remained significantly worse than competitors (29:1 ratio disadvantage)[16]