Several Months In — Here’s My Honest Feedback on Cursor

Lately I’ve been posting bug reports and feature requests here, so I thought it was time to also share some honest feedback about what it’s like to use Cursor — not just what’s missing.

I’ve been using Cursor for a few months now, and I can say without exaggeration:
it saves an enormous amount of time.
When you compare the value it delivers to its cost — especially for professional, paid development work — the time savings are massive.


1. Constant Upgrades

Cursor evolves incredibly fast.
Every time I imagine a new UI tweak or feature improvement, I usually find it already released within one or two versions. This kind of development velocity is rare.


2. Cursor vs. Alternatives

After the recent pricing changes across the industry, I tried almost every other alternative — yes, I even paid full price for many of them.
But in the end, I always had to come back to Cursor.

I’m not sure what Cursor’s “secret sauce” is — especially when competitors get a lot of positive marketing buzz — but the truth is, the same prompt, with the same model, in Cursor, actually works.
No bugs. No weird behavior. Just results.

With those same prompts, in other apps, it just… doesn’t.
I won’t name names, but I had to abandon many of the credits I purchased elsewhere because the tools didn’t deliver working results.

I do believe others will catch up someday — but for now, this is the reality.
(For the record, I don’t count tools that are just a thin terminal UI locked to a single provider — in my experience, no single model is good for everything.)


3. Customer Support

To be honest, the email support (hi@cursor) has been a really poor experience — the bot there almost never understands what I’m asking.
But when I post here in the forum, the responses are usually quick, clear, and helpful. So far, most of my issues have been resolved in a reasonable way.


4. Pricing and Auto Mode

True, we no longer pay “per request” — it’s all token-based now. But the Auto mode is still extremely useful.

For a large portion of my tasks — summarizing, navigating large codebases, understanding what other models are trying to do — Auto is often more than enough. And it feels unlimited.

I reserve the more expensive models for very specific or complex tasks.
Interestingly, I’ve also found some tricks to identify which model was actually used in Auto mode — and it’s helped me understand why Cursor doesn’t always reveal the model names. Their approach makes more sense to me now.


5. What’s Still Missing

Most frustrating: lack of credit/balance transparency.
There’s currently no reliable way to know how much I’ve spent this month, or how much I have left.
The dashboard shows all usage — including things from Auto mode that technically don’t count against your paid balance — which makes the numbers meaningless in practice.
I can only guess how much credit I have left, which is extremely frustrating. I hope this changes soon.

Second issue: editing & file cleanup.
Since billing is token-based, it would make a lot of sense to allow users to edit messages and remove file attachments before resending a prompt — to avoid unnecessary costs.
That option is currently missing and would make a big difference.


Final Thoughts

I spend over $200/month on Cursor — but I’m completing in a single hour tasks that used to take me a week.
I finish a month of work in a few days.
So yes — the benefits far outweigh the downsides. Especially when there’s no real competition right now.

That’s my honest review — maybe it helps someone else.
And thank you to the Cursor team for building such a powerful and focused tool.

8 Likes

Same experience for me. Cursor has occasionally been a bumpy ride but the things I can accomplish with it are just incredible.

Especially on days when my brain is totally fried so I can’t write lines of code, but I can write out in English what needs to happen. On those days, Cursor is worth any cost :joy:

2 Likes

Hi, thanks for the honest review :folded_hands:

Firstly, I appreciate the feedback on our email support. We’ve grown massively and as such, we’re working hard to grow our support team. We’re adding new members to the team each week, and will hopefully get our email support into a much better place - we are not at the level of support we want to be right now!

Regarding transparency, the team is working hard on this too. v1.3 is releasing shortly with a context window indicator - a small addition, but one that can help keep track of how large the context is that’s being sent to the model. More is on the way too to help with this in our next few releases!

I appreciate the idea about reducing the previous context when submitting a followup. I’ll pass this to the team, but a good workaround could be to start a new chat, and then use the @ menu to reference a summary of the old chat - you should be able to continue where you left off without the whole past conversation needing to be included!

Again, appreciate the time writing this our :folded_hands:

This is the most honest review I’ve seen about Cursor and I must say, my experience is same, I know I’ve achieved a lot of stuff with Cursor unlike other tools out there, really, Cursor is worth it.

2 Likes

Thank you very much!
Honestly, I didn’t know it was possible to do it the way you described I’ll try using that from now on.
But… the workflow feels much smoother when you just keep going and going until all the bugs are finally fixed.
My token window fills up very quickly
you can’t seriously expect me to start a new conversation every two messages.
That just breaks the flow completely.
But, thank you very much.

And I forgot to mention — I really appreciate what you wrote about email support.
There’s nothing like honesty, and it’s clear that you’re an amazing company, growing at an incredible pace.
I have no idea how many users you’re dealing with every day, but it seems like for every one who leaves, fifty new ones sign up — and eventually, even those who leave come back, because they realize there’s no real alternative.

So I completely understand how hard it must be to keep up with support.

But please allow me to make one small suggestion:

When I send you an email and the bot replies with generic and often unhelpful answers —
please add a line at the bottom saying something like:
“I’m a bot. I may not always get things right. If you want to reach a human, just let me know.”

Because when I don’t know it’s a bot, and it keeps replying with irrelevant or frustrating responses, it really drives me crazy.

3 Likes

That’s true, the only thing I’ve seen that’s needed is patience, reading all the code he wrote, whenever I decide to trust him completely, unpleasant things happen…

Thanks @yakovw I also appreciate your great feedback and suggestions. We will continue working on improvements in all areas. Please continue to send us feedback and any issues you find :slight_smile:

Thank you too, glad you read this.

1 Like

Hi Yakov,
Dov here. I’m a non-technical founder working to get my team to embrace AI—specifically, using Cursor for development.
What would you recommend as the best way to approach this?

Hi Dov,
Glad to hear from you.
To help me, I’ll need a lot more details, which are missing from what you wrote.
Are you not the technical person? Who is the team?
What are you working on?
Which programming language?
What budget are you looking to invest?
What knowledge does the team already have?