Cursor 2.0 - An unusable piece of ****

Warning: I hardly, ever, write reviews on products, so it takes a LOT to get me to this point. But:

Jesus Christ. What the hell happened here. Cursor 2.0 turned my user experience from being a fan of a great product to absolutely hating the product with every fibre of my body.

2.0 has made Cursor absolutely impossible to use.

  • Answers are broken/nonsensical/badly formatted (at best)
  • agent just stops in the middle of processes without any warning
  • everything takes FOREVER (seems like factor 5x), IF it works at all.
  • Where the old Cursor gave clearly formatted answers, I now always have to double check if the process is still running or that crppy output I’m seeing IS the actual answer.

In short, Cursor 2.0 is an unusable piece of horses*it.

If things don’t get better in the next days, I’m telling all of my employees to cancel their accounts, and switch to another solution. This is RIDICULOUS.

13 Likes

I think they’ll be okay without your $40.

2 Likes

I completely agree with your opinion because during my current usage, cursor suddenly stops responding. And it won’t output anything, as if the pause button has been pressed. I even signed up for a $200 ultra package for this, but so far, my experience has been very poor and my token has been consumed very quickly. My $400 token was used up in just two hours, and it won’t continue when I use the auto mode

2 Likes

The issues you’re facing it seems are local, as i’m getting prod-grade results and stability?

2.0 is a big jump, and I was super-sceptical about the new agent-focused interface, but after 24 hours I’m a convert, and very excited about the productivity gains with it!

1 Like

idk works on my machine :alien:

What models do you use? Nothing has changed for me with:

This is not a problem at all, as this interface can be switched. However, they decided to make it the first of the two, and that’s why it turned on first for all users after upgrading to 2.0.

People have been saying this for a year here. No exaggeration. Yet, for the entire year, they have complained on every update, but continued to pay, and use, and are still so involved they complain within the first 3-4 days of each update.

So, it can’t be that bad.

Vibe-coded software for vibe coders?

we complain exactly because WE USE IT and of course we like it.
So, yes, is that bad to mess things up in every update.

2 Likes

sounds like

1 Like

I don’t know. I definitely have my problems with Cursor - there are a lot of problems - but I don’t mind the change.

Hopefully they will get to a point where they stop making changes based on what they think people want instead of what people actually want. They could probably replace a couple of engineers with a couple of product managers for better product health.

I’m not saying that they don’t respond to requests, but the response is odd. For example, someone will make a big stink sot hey respond with a change but lots of other people don’t like it. A LOT of the complaints could be fixed with some focused product management that actually has the teeth to acquire, implement and analyze properly.

1 Like

I’ve been asking for the Agent’s terminal to be fixed for a very long time. When it started working almost perfectly, they completely broke it in another way. It took them 2-3 weeks to add a checkmark that could be used to return the old behavior (legacy terminal).

They break the UX even in patches, not just in major updates.

2 Likes

@andrewh sorry if I crossed the line, but it honestly hurts to see how often something breaks inside Cursor. We’re all developers here — bugs happen all the time — but there are methods specifically meant to keep them to a minimum.

1 Like

For the terminal issue, could you provide as detailed steps as possible for someone to try and reproduce and fix it?

Already fixed. I use legacy terminal now and all fine.