Performance Issues After Upgrading to $200 Ultra Plan

Support Bug Reports
1

Describe the Bug

I’ve been using Cursor for a while now to build an app I’m actively working on and I’ve been consistently impressed with how well it understands and helps implement my ideas. It’s become a core part of my daily workflow and I’ve been on the Pro plan for months without any major issues. The model I used “Claude Sonnet 4 in Max Thinking Mode” has always handled my app requests efficiently, usually completing them accurately in just one prompt.

However, since upgrading to the $200 per month Ultra plan last week, my experience has drastically changed, for the worse.

Tasks that used to be completed in one clean attempts now often take 4 or 5 tries. Even worse, the agent often skips or ignores parts of the task entirely, asking me to re prompt to continue where it left off. This is extremely frustrating, especially considering I’m still using “Max Thinking Mode” with the same model and same prompts I was using before the upgrade.

To be clear: nothing about how I’m using the tool has changed, only my plan and coincidentally Cursor’s latest update. I initially switched from the “Usage Based Pricing” model to test whether the Ultra Plan would be more convenient but instead I’ve experienced degraded performance, slower iteration and increased frustration.

It honestly feels like I’m now paying more for a worse experience. If anyone else has experienced a similar drop in agent performance after upgrading or has any insight into this, I’d really appreciate your assistance.

Steps to Reproduce

  1. Upgrade from Pro or Usage-Based plan to the $200/month Ultra plan
  2. Use Claude Sonnet 4 in Max Thinking Mode
  3. Prompt the agent with a task it previously completed successfully in one attempt
  4. Observe degraded performance: incomplete responses, skipped steps and repeated need to re-prompt to finish the same task I was able to in 1-2 prompts before upgrading.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.4
VSCode Version: 1.99.3
Commit: a8e95743c5268be73767c46944a71f4465d05c90
Date: 2025-07-10T16:53:59.659Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 23.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.