Concerns Regarding Cursor's Recent Plan Changes

I want to express my discomfort with the recent billing model changes in Cursor, specifically regarding the shift towards rate-limit-based pricing.

My primary concern is the lack of transparency in the new billing approach. The specific rules and limits for rate-limiting are not clearly disclosed, and there is no straightforward way for users to monitor their current usage in real-time. Without this transparency, it becomes difficult for me to effectively plan and allocate my work based on anticipated usage.

Due to these uncertainties, I opted to switch back to the previous billing model. Even though my overall usage might end up lower compared to the new plan, I prefer having control over my workflow planning. However, I’ve encountered another issue: the detailed usage breakdown for each individual call is no longer visible in the dashboard. Additionally, the documentation no longer provides explicit pricing details for individual models, which further adds to my confusion.

While I understand that Cursor might be aiming to reduce operational costs through these adjustments, I strongly believe the focus should instead be placed on preventing misuse and abuse, rather than introducing opaque billing methods that inadvertently inconvenience genuine users.

I’m curious to hear others’ thoughts and whether you’re experiencing similar issues with these recent changes.

2 Likes

I’m currently waiting and enjoying unlimited tool calls, there are other issues like users reporting increased credits usage that may be linked to this change, overall I see most of us agree this was a rushed feature, to cursor: we’re already in a fast-paced evolving spiral, please, ease our work.

Edit: Found some info about new rate limits: Bad Usage Reporting on 3rd Party Extension - #24 by Zackh1998

if you made a word cloud the three biggest words on this forum would be:

Rate
Billing
Transparency

it’s wild to continue to watch this after literally 6 months of mentioning features and decisions and why they are objectively an invisible cost to the consumer while they push version tipping commits that further confuse us when we directly ask questions with easy answers