First use of paid plan a huge disappointment

Did a few days of testing with a couple small projects and things seemed fine. Just upgraded to paid. The honeymoon allready over.

Long story short: I’m wasting fast requests. It can’t decide what files it needs, how to install dependencies, it started deleting files at random, then rewrote them in the incorrect location. These are things it knew how to do this morning.

I thought long and hard about going down the Cline path. If this behavior is what I can expect from Cursor, I most certainly will only pay for the single month and pivot.

Thanks for letting me vent.

1 Like

We’ve all been there at the start, completing fast requests in 2 days. With time and study, you reach a point where research and codebase understanding become your main time-consuming tasks. This is the way forward as our ability to learn quickly becomes the primary focus. From your message, it seems something changed. If it was a Cursor update, then go back to a safe option like 0.45 and check how to stop updates until you want to update. The alternative is to pay a lot more as Cline sends all your code, since it doesn’t have a trained model on how to use less context, or to be less productive as no other tool beats Cursor (feel free to try them).

1 Like

I’ve just asked for a refund, since the updates in past couple days the whole app is unusable.

1 Like

How long have you been using it? In reviewing this forum, it appears that the 0.46 version, combined with Claude 3.7, has been problemmatic. Did this start after the update?

I used cursor for 1 year and I totally hate last update. Agent is worse than it was and doesn’t matter if sonnet 3.5 or 3.7. I mostly ■■■■■■ they now don’t provide non agent mode with apply button. Also UX is worse and they don’t update current open file in context so have to delete previous file and add manually new. I already unsubscribed today and once expires and if this not fixed then will look for better pasture.

Yes, for a lot of people 0.46 has been breaking context, probably because it has a new llm model for context… its true that they could have handled a better upgrading strategy and I bet they will learn the lesson as the community was harsh… still I don’t get people like @Bandersen or @pzo asking refunds or not renewing like 0.46 is a breaking through and they cannot work without, just go with 0.45 and wait for stability, its that simple

it’s not not that simple - I already rolled back to 0.45 and being careful and avoided too click update button but then after restart my macbook it updated automatically. I can even forgive that they screwed up, but cannot forgive that they put everything under the rug and head in the sand - there is no official statement and still rolling everything down the throat to everyone. This is just bad way of handling it, they should put official statement what went bad etc and whats their plan and how they plan to avoid it to regain confidence.

1 Like

research about downgrading and you’ll see its simple, there’s an option to stop updating, I agree with you we deserve more communication, I think they found themselves overwhelmed between testing 0.46 and adding 3.7 but still more communication is needed