Jump to content

CursorAI adds rate limits to unlimited plans: Difference between revisions

From Consumer Rights Wiki
Fixed the categories.
Rudxain (talk | contribs)
m link AI
Tags: Mobile edit Mobile web edit Advanced mobile edit Visual edit
 
(12 intermediate revisions by 9 users not shown)
Line 1: Line 1:
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.<ref>{{Cite web |title=Developer Reports Cursor AI Plan Change and Lockouts |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028 |access-date=2025-07-05}}</ref>
{{Incomplete}}
{{IncidentCargo
|Company=Anysphere
|StartDate=2025-06
|EndDate=
|Status=
|ProductLine=
|Product=CursorAI
|ArticleType=Product
|Type=Artificial Intelligence, Rent-seeking
|Description=
}}
Cursor AI silently changed their ''"unlimited"'' Pro plan to severely [[wikipedia:Rate_limiting|rate-limited]] without notice, locking users out after 3-7 requests & forcing them to upgrade to regain functionality.<ref>{{Cite web |title=Developer Reports Cursor AI Plan Change and Lockouts |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>


==Background==
==Background==
Cursor AI, a developer-focused AI code assistant, marketed its $20/month Pro plan with "Unlimited Agent Requests,"<ref>{{Cite web |title=Cursor Pricing Page Archive |url=https://web.archive.org/web/20250222054643/https://www.cursor.com/en/pricing |access-date=2025-07-05}}</ref> targeting professional developers who depend on advanced models like 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.
Cursor AI, a developer-focused [[Artificial intelligence|AI]] code assistant, marketed its $20/month Pro plan with "Unlimited Agent Requests,"<ref>{{Cite web |title=Cursor Pricing Page Archive |url=https://web.archive.org/web/20250222054643/https://www.cursor.com/en/pricing |access-date=2025-07-05}}</ref> 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<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}}</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}}</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]]
[[File:CursorAI 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==
===Silent Plan Changes===
===Silent plan changes===
Days after June 16, 2025, launch, Cursor quietly walked back ''"Unlimited Agent Requests"''
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"''
*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:<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}}</ref>
On June 16, 2025, Cursor AI pushed through large changes to their Pro Plan terms without properly notifying customers:<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>


*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}}</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:CursorAI 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:CursorAI updated pricing 3 July 2025.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}}</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>


===User Impact===
===User impact===
Users began experiencing unexpected rate limiting with minimal usage:
Users began experiencing unexpected rate limiting with minimal usage:


*Users reported being rate limited after few requests to Claude 4 Sonnet
*Users reported being rate limited after few requests to Claude 4 Sonnet
*Rate limits lasted 5-24 hours despite documentation claiming ''"every few hours"'' reset periods<ref>{{Cite web |title=User Report: 26 Hour Rate Limit |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/45 |access-date=2025-07-05}}</ref>
*Rate limits lasted 5-24 hours despite documentation claiming ''"every few hours"'' reset periods<ref>{{Cite web |title=User Report: 26 Hour Rate Limit |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/45 |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>
*No advance warning when approaching limits or specific indication of when the limits would reset
*No advance warning when approaching limits or specific indication of when the limits would reset
*Dashboard showed usage events but no dollar consumption tracking against monthly allowance
*Dashboard showed usage events but no dollar consumption tracking against monthly allowance
*Sudden transitions from ''"included in Pro"'' usage to expensive pay-as-you-go billing without warning.
*Sudden transitions from ''"included in Pro"'' usage to expensive pay-as-you-go billing without warning.


===Suppression of Customer Complaints===
===Suppression of customer complaints===
The company suppressed customer complaints:
The company suppressed customer complaints:


*AI moderation system repeatedly hid customer complaint threads from public view<ref>{{Cite web |title=Reports of Forum Shadowbans |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/48 |access-date=2025-07-05}}</ref>
*AI moderation system repeatedly hid customer complaint threads from public view<ref>{{Cite web |title=Reports of Forum Shadowbans |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/48 |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>
*Professional, well-documented complaints became unsearchable on the forum<ref>{{Cite web |title=Forum Thread Hidden By Moderation |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/48 |access-date=2025-07-05}}</ref>
*Professional, well-documented complaints became unsearchable on the forum<ref>{{Cite web |title=Forum Thread Hidden By Moderation |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/48 |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>
*Staff dismissed documented evidence as ''"conspiracy theories"''<ref>{{Cite web |title=Dismissal of Complaints |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/60 |access-date=2025-07-05}}</ref>
*Staff dismissed documented evidence as ''"conspiracy theories"''<ref>{{Cite web |title=Dismissal of Complaints |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/60 |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>
*Multiple threads documenting the issues were shadow-banned or made invisible to new users
*Multiple threads documenting the issues were shadow-banned or made invisible to new users


==Cursor's response==
==Cursor's response==
===Initial denial & suppression===
===Initial denial and suppression===
Cursor AI's initial responses were inadequate & dismissive:
Cursor AI's initial responses were inadequate and dismissive:


*Customer support provided canned responses that ignored specific questions about timing & usage numbers<ref>{{Cite web |title=Template Support Responses |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/62 |access-date=2025-07-05}}</ref>
*Customer support provided canned responses that ignored specific questions about timing & usage numbers<ref>{{Cite web |title=Template Support Responses |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/62 |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>
*Staff members dismissed user concerns as ''"conspiracy theories"'' despite documented evidence<ref>{{Cite web |title=Staff Responses to Rate Limit Complaints |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/43 |access-date=2025-07-05}}</ref>
*Staff members dismissed user concerns as ''"conspiracy theories"'' despite documented evidence<ref>{{Cite web |title=Staff Responses to Rate Limit Complaints |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/43 |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>
*AI moderation system continued hiding customer complaint threads<ref>{{Cite web |title=Ongoing Forum Suppression |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/37 |access-date=2025-07-05}}</ref>
*AI moderation system continued hiding customer complaint threads<ref>{{Cite web |title=Ongoing Forum Suppression |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/37 |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>


===Official Damage Control Response===
===Official damage control response===
On July 5, 2025, facing overwhelming cross-platform pressure, Cursor AI published a blog post acknowledging the issues:
On July 5, 2025, facing overwhelming cross-platform pressure, Cursor AI published a blog post acknowledging the issues:


*Admitted that ''"unlimited usage"'' was misleading and only applied to inferior Auto mode, not direct model access<ref>{{Cite web |title=Cursor Clarifies Misleading Unlimited Claims |url=https://forum.cursor.com/t/clarifying-june-16-pro-changes/111740 |access-date=2025-07-05}}</ref>
*Admitted that ''"unlimited usage"'' was misleading and only applied to inferior Auto mode, not direct model access<ref>{{Cite web |title=Cursor Clarifies Misleading Unlimited Claims |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>
*Clarified that Pro plan includes approximately 225 Sonnet 4 requests per month (down from previously advertised unlimited)
*Clarified that Pro plan includes approximately 225 Sonnet 4 requests per month (down from previously advertised unlimited)
*Offered full refunds for unexpected charges between June 16 and July 4, 2025
*Offered full refunds for unexpected charges between June 16 and July 4, 2025
*Updated documentation to provide more specific limit information, though still vague on reset timing
*Updated documentation to provide more specific limit information, though still vague on reset timing


===Continued Problems===
===Continued problems===
Even after the official response, fundamental issues remained unresolved:
Even after the official response, fundamental issues remained unresolved:


Line 59: Line 71:
*Reset timing described vaguely as ''"5-24 hours"'' with no guarantees (''"best-effort basis"'')
*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
*No real-time usage tracking implementation to help users manage consumption
*[[File:Forum screenshot.jpg|thumb|Forum user doing math to demonstrate how cursor is 29x worse than claude]]Value proposition remained significantly worse than competitors (29:1 ratio disadvantage)<ref>{{Cite web |title=Comparison with Competitors |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/64 |access-date=2025-07-05}}</ref>
*[[File:CursorAI screenshot of forum post.jpg|thumb|Forum user doing math to demonstrate how cursor is 29x worse than claude]]Value proposition remained significantly worse than competitors (29:1 ratio disadvantage)<ref>{{Cite web |title=Comparison with Competitors |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/64 |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>


==Consumer response==
==Consumer response==
===Cross-Platform Documentation===
===Cross-platform documentation===
The consumer backlash spread to multiple platforms:
The consumer backlash spread to multiple platforms:


*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}}</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 |url-status=live |archive-url=https://web.archive.org/web/20260415184215/https://nitter.catsarch.com/0ni_x4/status/1940885976127283342 |archive-date=15 Apr 2026 |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>
*Community-maintained archives created due to forum censorship and thread hiding<ref>{{Cite web |title=Archive of Hidden Threads |url=https://web.archive.org/web/20260218083327/https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/ |url-status=live |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===
Affected consumers took direct action:
Affected consumers took direct action:


*Mass cancellations of annual subscriptions with refund requests<ref>{{Cite web |title=User Reports Cancellations |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/83 |access-date=2025-07-05}}</ref>
*Mass cancellations of annual subscriptions with refund requests<ref>{{Cite web |title=User Reports Cancellations |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/83 |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>
*Migration to transparent alternatives like Claude Code Pro '''(which offered 29x better value)'''<ref>{{Cite web |title=Discussion on Switching to Competitors |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/85 |access-date=2025-07-05}}</ref>
*Migration to transparent alternatives like Claude Code Pro '''(which offered 29x better value)'''<ref>{{Cite web |title=Discussion on Switching to Competitors |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/85 |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>
*Organized documentation efforts to preserve evidence of service changes<ref>{{Cite web |title=User Documentation Efforts |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/87 |access-date=2025-07-05}}</ref>
*Organized documentation efforts to preserve evidence of service changes<ref>{{Cite web |title=User Documentation Efforts |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/87 |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>
*Cross-platform pressure campaign that ultimately forced the company's official response<ref>{{Cite web |title=Pressure Leading to Official Response |url=https://forum.cursor.com/t/clarifying-june-16-pro-changes/111740 |access-date=2025-07-05}}</ref>
*Cross-platform pressure campaign that ultimately forced the company's official response<ref>{{Cite web |title=Pressure Leading to Official Response |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>
*Users sharing workarounds like reverting to "legacy pricing" where available<ref>{{Cite web |title=Users Reverting to Legacy Pricing |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/90 |access-date=2025-07-05}}</ref>
*Users sharing workarounds like reverting to "legacy pricing" where available<ref>{{Cite web |title=Users Reverting to Legacy Pricing |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/90 |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>


===Consumer Impact===
===Consumer impact===
CursorAI's actions seriously disrupted pro developer's workflows:
CursorAI's actions seriously disrupted pro developer's workflows:


*Developers experienced sudden 26-hour lockouts during critical project work
*Developers experienced sudden 26-hour lockouts during critical project work
*Users forced to switch to inferior Auto mode or stop their dev work completely
*Users forced to switch to inferior Auto mode or stop their dev work completely
*Anxiety around usage due to unpredictable enforcement & billing<ref>{{Cite web |title=User Anxiety Over Enforcement |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/95 |access-date=2025-07-05}}</ref>
*Anxiety around usage due to unpredictable enforcement & billing<ref>{{Cite web |title=User Anxiety Over Enforcement |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/95 |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>
*Loss of confidence in service reliability for professional development work
*Loss of confidence in service reliability for professional development work
*Financial pressure to upgrade to $60+ plans to regain previously advertised functionality
*Financial pressure to upgrade to $60+ plans to regain previously advertised functionality


===Community Sentiment===
===Community sentiment===
Documented consumer sentiment included:
Documented consumer sentiment included:


*Accusations of '''"rug-pull"''' & bait-and-switch tactic.
*Accusations of '''"rug-pull"''' & bait-and-switch tactic.
*Comparisons to "snake oil salesmen" and predatory business practices<ref>{{Cite web |title=Snake Oil Comparisons |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/83 |access-date=2025-07-05}}</ref>
*Comparisons to "snake oil salesmen" and predatory business practices<ref>{{Cite web |title=Snake Oil Comparisons |url=https://forum.cursor.com/t/pro-plan-rate-limit-transparency-issues-need-specific-usage-details/113028/83 |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>
*Calls for transparency in billing and usage tracking
*Calls for transparency in billing and usage tracking
*Demands for honest marketing that doesn't rely on technical loopholes
*Demands for honest marketing that doesn't rely on technical loopholes
*Recognition that the incident represented broader anti-consumer trends in AI services
*Recognition that the incident represented broader anti-consumer trends in AI services
==See also==
*[[Post-purchase EULA modification]]


==References==
==References==
{{reflist}}
{{Reflist}}


[[Category:Cursor]]
[[Category:Cursor]]
[[Category:Artificial intelligence]]
[[Category:Artificial intelligence]]

Latest revision as of 18:07, 19 April 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 ▼

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]

Background

[edit | edit source]

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.

Service degradation and consumer exploitation

[edit | edit source]

Silent plan changes

[edit | edit source]

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" line
    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[7]

User impact

[edit | edit source]

Users began experiencing unexpected rate limiting with minimal usage:

  • Users reported being rate limited after few requests to Claude 4 Sonnet
  • Rate limits lasted 5-24 hours despite documentation claiming "every few hours" reset periods[8]
  • No advance warning when approaching limits or specific indication of when the limits would reset
  • Dashboard showed usage events but no dollar consumption tracking against monthly allowance
  • Sudden transitions from "included in Pro" usage to expensive pay-as-you-go billing without warning.

Suppression of customer complaints

[edit | edit source]

The company suppressed customer complaints:

  • AI moderation system repeatedly hid customer complaint threads from public view[9]
  • Professional, well-documented complaints became unsearchable on the forum[10]
  • Staff dismissed documented evidence as "conspiracy theories"[11]
  • Multiple threads documenting the issues were shadow-banned or made invisible to new users

Cursor's response

[edit | edit source]

Initial denial and suppression

[edit | edit source]

Cursor AI's initial responses were inadequate and dismissive:

  • Customer support provided canned responses that ignored specific questions about timing & usage numbers[12]
  • Staff members dismissed user concerns as "conspiracy theories" despite documented evidence[13]
  • AI moderation system continued hiding customer complaint threads[14]

Official damage control response

[edit | edit source]

On July 5, 2025, facing overwhelming cross-platform pressure, Cursor AI published a blog post acknowledging the issues:

  • Admitted that "unlimited usage" was misleading and only applied to inferior Auto mode, not direct model access[15]
  • Clarified that Pro plan includes approximately 225 Sonnet 4 requests per month (down from previously advertised unlimited)
  • Offered full refunds for unexpected charges between June 16 and July 4, 2025
  • Updated documentation to provide more specific limit information, though still vague on reset timing

Continued problems

[edit | edit source]

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 claude
    Value proposition remained significantly worse than competitors (29:1 ratio disadvantage)[16]

Consumer response

[edit | edit source]

Cross-platform documentation

[edit | edit source]

The consumer backlash spread to multiple platforms:

  • A detailed 51-page forum thread documented user experiences with screenshots, usage data, and technical analysis[17]
  • twitter post from disgruntled customer of cursorai
    Hundreds of complaints across Twitter/X from developers worldwide experiencing identical issues[18]
  • Community-maintained archives created due to forum censorship and thread hiding[19]
  • Reddit discussions confirming the same problems across the user base[20]

User actions

[edit | edit source]

Affected consumers took direct action:

  • Mass cancellations of annual subscriptions with refund requests[21]
  • Migration to transparent alternatives like Claude Code Pro (which offered 29x better value)[22]
  • Organized documentation efforts to preserve evidence of service changes[23]
  • Cross-platform pressure campaign that ultimately forced the company's official response[24]
  • Users sharing workarounds like reverting to "legacy pricing" where available[25]

Consumer impact

[edit | edit source]

CursorAI's actions seriously disrupted pro developer's workflows:

  • Developers experienced sudden 26-hour lockouts during critical project work
  • Users forced to switch to inferior Auto mode or stop their dev work completely
  • Anxiety around usage due to unpredictable enforcement & billing[26]
  • Loss of confidence in service reliability for professional development work
  • Financial pressure to upgrade to $60+ plans to regain previously advertised functionality

Community sentiment

[edit | edit source]

Documented consumer sentiment included:

  • Accusations of "rug-pull" & bait-and-switch tactic.
  • Comparisons to "snake oil salesmen" and predatory business practices[27]
  • Calls for transparency in billing and usage tracking
  • Demands for honest marketing that doesn't rely on technical loopholes
  • Recognition that the incident represented broader anti-consumer trends in AI services

See also

[edit | edit source]

References

[edit | edit source]
  1. "Developer Reports Cursor AI Plan Change and Lockouts". Archived from the original on 10 Jul 2025. Retrieved 2025-07-05.
  2. "Cursor Pricing Page Archive". Retrieved 2025-07-05.
  3. "Clarifying June 16 Pro Changes". Archived from the original on 17 Dec 2025. Retrieved 2025-07-05.
  4. "Cursor Community Discussion: No Usage Tracking". Archived from the original on 10 Jul 2025. Retrieved 2025-07-05.
  5. "Clarifying June 16 Pro Changes". Archived from the original on 17 Dec 2025. Retrieved 2025-07-05.
  6. "Cursor Documentation on Rate Limits". Archived from the original on 16 Feb 2026. Retrieved 2025-07-05.
  7. "User Complaints About Lack of Usage Dashboard". Archived from the original on 10 Jul 2025. Retrieved 2025-07-05.
  8. "User Report: 26 Hour Rate Limit". Archived from the original on 10 Jul 2025. Retrieved 2025-07-05.
  9. "Reports of Forum Shadowbans". Archived from the original on 10 Jul 2025. Retrieved 2025-07-05.
  10. "Forum Thread Hidden By Moderation". Archived from the original on 10 Jul 2025. Retrieved 2025-07-05.
  11. "Dismissal of Complaints". Archived from the original on 10 Jul 2025. Retrieved 2025-07-05.
  12. "Template Support Responses". Archived from the original on 10 Jul 2025. Retrieved 2025-07-05.
  13. "Staff Responses to Rate Limit Complaints". Archived from the original on 10 Jul 2025. Retrieved 2025-07-05.
  14. "Ongoing Forum Suppression". Archived from the original on 10 Jul 2025. Retrieved 2025-07-05.
  15. "Cursor Clarifies Misleading Unlimited Claims". Archived from the original on 17 Dec 2025. Retrieved 2025-07-05.
  16. "Comparison with Competitors". Archived from the original on 10 Jul 2025. Retrieved 2025-07-05.
  17. "Pro Plan Rate Limit Transparency Issues - Cursor Forum". Archived from the original on 10 Jul 2025. Retrieved 2025-07-05.
  18. "Developer Complaints on Twitter". Archived from the original on 15 Apr 2026. Retrieved 2025-07-05.
  19. "Archive of Hidden Threads". Retrieved 2025-07-05.{{cite web}}: CS1 maint: url-status (link)
  20. "Reddit User Reports on Cursor Rate Limits". Archived from the original on 23 Feb 2026. Retrieved 2025-07-05.
  21. "User Reports Cancellations". Archived from the original on 10 Jul 2025. Retrieved 2025-07-05.
  22. "Discussion on Switching to Competitors". Archived from the original on 10 Jul 2025. Retrieved 2025-07-05.
  23. "User Documentation Efforts". Archived from the original on 10 Jul 2025. Retrieved 2025-07-05.
  24. "Pressure Leading to Official Response". Archived from the original on 17 Dec 2025. Retrieved 2025-07-05.
  25. "Users Reverting to Legacy Pricing". Archived from the original on 10 Jul 2025. Retrieved 2025-07-05.
  26. "User Anxiety Over Enforcement". Archived from the original on 10 Jul 2025. Retrieved 2025-07-05.
  27. "Snake Oil Comparisons". Archived from the original on 10 Jul 2025. Retrieved 2025-07-05.