Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cursor IDE support hallucinates lockout policy, causes user cancellations

old.reddit.com

Post reply on HN
Print view View original

271–280 of 635 posts

Re: Cursor IDE support hallucinates lockout policy, causes user cancellations

#271

Post by daemonologist »

itissid wrote: post #254
daemonologist wrote: post #86

Earlier quoted context omitted.

AI companies high on their own supply, that's who. Ultralytics is (in)famous for it.

Why is Ultralytics yolo famous for it?

They had a bot, for a long time, that responded to every github issue in the persona of the founder and tried to solve your problem. It was bad at this, and thus a huge proportion of people who had a question about one of their yolo models received worse-than-useless advice "directly from the CEO," with no disclosure that it was actually a bot.

The bot is now called "UltralyticsAssistant" and discloses that it's automated, which is welcome. The bad advice is all still there though.

(I don't know if they're really _famous_ for this, but among friends and colleagues I have talked to multiple people who independently found and were frustrated by the useless github issues.)

Re: Cursor IDE support hallucinates lockout policy, causes user cancellations

#272

Post by mntruell »

(Cursor cofounder)

Apologies - something very clearly went wrong here. We’ve already begun investigating, and some very early results:

* Any AI responses used for email support are now clearly labeled as such. We use AI-assisted responses as the first filter for email support.

* We’ve made sure this user is completely refunded - least we can do for the trouble.

For context, this user’s complaint was the result of a race condition that appears on very slow internet connections. The race leads to a bunch of unneeded sessions being created which crowds out the real sessions. We’ve rolled out a fix.

Appreciate all the feedback. Will help improve the experience for future users.

Re: Cursor IDE support hallucinates lockout policy, causes user cancellations

#273

Post by VenturingVole »

sillyfluke wrote: post #221
cryptoegorophy wrote: post #180

Earlier quoted context omitted.

I think that’s why Apple is very slow at rolling out AI if it ever actually will. Downside is way too big than the upside.

They already rolled out an "AI" product. Got humiliated pretty bad, and rolled it back. [0] [0] https://www.bbc.com/news/articles/cq5ggew08eyo

They had an opportunity to actually adapt, to embrace getting rapid feedback/iterating: But they are not equipped for it culturally. Major lost opportunity as it could have been a driver of internal change.

I'm certain they'll get it right soon enough though. People were writing off Google in terms of AI until this year.. and oh how attitudes have changed.

Re: Cursor IDE support hallucinates lockout policy, causes user cancellations

#274

Post by VenturingVole »

zdragnar wrote: post #222
cryptoegorophy wrote: post #180

Earlier quoted context omitted.

I think that’s why Apple is very slow at rolling out AI if it ever actually will. Downside is way too big than the upside.

Investors seem to be starved for novelty right now. Web 2.0 is a given, web 3.0 is old, crypto has lost the shine, all that's left to jump on at the moment is AI. Apple fumbled a bit with Siri, and I'm guessing they're not too keen to keep chasing everyone else, since outside of limited applications it turns out half baked at best. Sadly, unless something shinier comes along soon, we're going to have to accept that e…

"all that's left to jump on at the moment is AI" -> No, it's the effective applications of AI. It's unprecedented.

I was in the VC space for a while previously, most pitch decks claimed to be using AI: But doing even the briefest of DD - it was generally BS. Now it's real.

With respect to everything being awful: One might say that's always been the case. However, now there's a chance (and requirement) to build in place safeguards/checks/evals and massively improve both speed and quality of services through AI.

Don't judge for the problems: Look at the exponential curve, think about how to solve the problems. Otherwise, you will get left behind.

Re: Cursor IDE support hallucinates lockout policy, causes user cancellations

#275

Post by [deleted] »

pfg_ wrote: post #134
adriand wrote: post #55

Earlier quoted context omitted.

VS Code with standard copilot for tab completion and Aider in a terminal window for all the heavier lifts, asking questions, architecting etc. And it’s cheap! I’ve been using it with OpenRouter (lets you easily switch models and providers) and my $10 of credits lasted weeks. Granted, I also use Claude a lot in the browser.

Copilot's tab completion is significantly worse than cursor's in my experience (only tried free copilot)

[deleted]

Re: Cursor IDE support hallucinates lockout policy, causes user cancellations

#276

Post by ericwood »

tptacek wrote: post #249
ericwood wrote: post #246

Earlier quoted context omitted.

Hey both things can be true. It’s a long ways from the AI renaissances of the past. There’s areas LLMs make a lot of sense. I just don’t find them to be great pair programming partners yet.

I think people are kind of kidding themselves here. For Go and Python, two extraordinarily common languages in production software, it would be weird for me at this point not to start with LLM output. Actually building an entire application, soup-to-nuts, vibe-code style? No, I wouldn't do that. But having the LLM writing as much as 80% of the code, under close supervision, with a careful series of prompts (like, "ok…

I'm glad that works for you. Ultimately I think different people will prefer different ways of working. Often when I'm starting a new project I have lots of boilerplate from previous ones I can bootstrap off of. If it's a new tool I'm unfamiliar with I prefer to stumble through it, otherwise I never fully get my head around it. This tends to not look like insane levels of productivity, but I've always found in the long run time spent scratching my head or writing awkward code over and over again (Rust did this to me a lot in the early days) ends up paying off huge dividends in the long run, especially when it's code I'm on the hook for.

What I've found frustrating about the narrative around these tools; I've watched them from afar with intrigue but ultimately found that method of working just isn't for me. Over the years I've trialed more tools than I can remember and adopted the ones I found useful, while casting aside ones that aren't a great fit. Sometimes I find myself wandering back to them once they're fully baked. Maybe that will be the case here, but is it not valid to say "eh...this isn't it for me"? Am I kidding myself?

Re: Cursor IDE support hallucinates lockout policy, causes user cancellations

#277

Post by hombre_fatal »

mgraczyk wrote: post #114

What is the evidence that "dozens of users publicly canceled their subscriptions"? A total of 4 users claimed that they did or would cancel their subscriptions in the comments, and 3/4 of them hedged by saying that they would cancel if this problem were real or happened to them. It looks like only 1 person claimed to have cancelled already. Is there some other discussion you're looking at?

Yeah, it's a reddit thread with 59 comments.

Yet if you went by the HN comments, you'd think it were the biggest item on primetime news.

People are really champing at the bit.

Re: Cursor IDE support hallucinates lockout policy, causes user cancellations

#278

Post by anonzzzies »

nerdjon wrote: post #63

There is a certain amount of irony that people try really hard to say that hallucinations are not a big problem anymore and then a company that would benefit from that narrative gets directly hurt by it. Which of course they are going to try to brush it all away. Better than admitting that this problem very much still exists and isn’t going away anytime soon.

Did anyone say that? They are an issue everywhere, including for code. But with code at least I can have tooling to automatically check and feed back that it hallucinated libraries, functions etc, but with just normal research / problems there is no such thing and you will spend a lot of time verifying everything.

Re: Cursor IDE support hallucinates lockout policy, causes user cancellations

#279

Post by ModernMech »

schmichael wrote: post #168
yodsanklai wrote: post #131

Earlier quoted context omitted.

You're not supposed to trust the tool, you're supposed to review and rework the code before submitting for external review. I use AI for rather complex tasks. It's impressive. It can make a bunch of non-trivial changes to several files, and have the code compile without warnings. But I need to iterate a few times so that the code looks like what I want. That being said, I also lose time pretty regularly. There's a le…

> You're not supposed to trust the tool This is just an incredible statement. I can't think of another development tool we'd say this about. I'm not saying you're wrong, or that it's wrong to have tools we can't just, just... wow... what a sea change.

Imagine! Imagine if 0.05% of the time gcc just injected random code into your binaries. Imagine, you swing a hammer and 1% of the time it just phases into the wall. Tools are supposed to be reliable.

Re: Cursor IDE support hallucinates lockout policy, causes user cancellations

#280

Post by ModernMech »

andrei_says_ wrote: post #244
ryandrake wrote: post #212

Earlier quoted context omitted.

Imagine if your compiler just randomly and non-deterministically compiled valid code to incorrect binaries, and the tool's developer couldn't really tell you why it happens, how often it was expected to happen, how severe the problem was expected to be, and told you to just not trust your compiler to create correct machine code. Imagine if your calculator app randomly and non-deterministically performed arithmetic in…

Imagine that you yourself never use these tools directly but your employees do. And the sellers of said tools swear that the tools are amazing and correct and will save you millions. They keep telling you that any employee who highlights problems with the tools are just trying to save their job. Your investors tell you that the toolmakers are already saving money for your competitors. Now, do you want that second hou…

I feel like there's a lot of motivated reasoning going on, yeah.
Post reply on HN