Live data from Hacker News

Cursor IDE support hallucinates lockout policy, causes user cancellations

old.reddit.com

311–320 of 635 posts

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

#311

Earlier quoted context omitted.

Hi Michael, Slightly related to this; I just wanted to ask whether all Cursor email inboxes are gated by AI agents? I've tried to contact Cursor via email a few times in the past, but haven't even received an AI response :) Cheers!

Not all of them (e.g. security@)! But our support system currently is. We are standing up a much bigger team here but are behind where we should be.

filtering (besides spam) and answering emails is a place where AI agents shouldn't be imho

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

#312

(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 r…

Support emails shouldn't be AI. It's just so annoying. Put a human in the loop at least. This is a paying service, not a massive ad supported thing.

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

#313

Cursor sucks. Not as a product. As a team. Their customer support is terrible. I was offered in writing a refund by the team who cold reached out to me to ask me why I cancelled my sub one week after start. Then they ignored my 3+ emails in response asking them to refund, and other means of trying to communicate with them. Offering me a refund as a bait to gain me back, then when I accept it they ghost me. Wow. Very…

This reminds me of how small of a team they are, and makes me wonder if they have a customer support team that's growing commensurately with the size of the user base.

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

#314
post #286

(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 r…

You’ve promised a ton of people refunds that never got them. Others in this thread, and myself included Edit: he did refund 22 mins after seeing this

you didn't get a refund because the promise of refund was also hallucinated.

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

#315
I was playing around with ChatGPT the other day and encountered a similar issue. Once I hit the rate limit, the replies telling me that seemed to be AI generated. When I waited the requisite time, the next use attempt repeated the last message about being past the limit and needing to wait 13 hours again.

It seemed to be reading from the conversation to determine this. Oops! Replaying an earlier message worked fine.

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

#317
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.

You get some superficial checking by the compiler and test cases, but hallucinations that pass both are still an issue.

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

#318

Earlier quoted context omitted.

That’s a pretty mean spirited way to approach this subject. I think the creators of Redis and Django are very capable and self-respecting software developers.

[flagged]

I know my work and it largely isn't shoddy. I have a keen eye for detail and code quality is incredibly important to me. But yeah, I am lazy and I hate wasting my time. AI has been a huge boon in the amount of time it's saved me.

> And the vast majority of people using them are either too stupid or too lazy to actually review their own output.

I don't know if that's true or not. But I'm not stupid or too lazy to review the code, because I review every line and make sure I understand everything. The same way I do with every line of my own code or every line a colleague writes if it's relevant to what I'm working on.

You're in the wrong place if you want to talk about people, particularly fellow developers, in this way. You're just being toxic.

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

#319

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.

You say slowly, but in my opinion Apple made an out of character misstep by releasing a terrible UX to everyone. Apple intelligence is a running joke now. Yes they didn't push it as hard as, say, copilot. I still think they got in way too deep way too fast.

Remember „You are a bad user, I am a good bing“? Apple is just slower in fixing and improving things.

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

#320

LLM anything makes me queasy. Why would any self respecting software developer use this tripe? Learn how to write good software. Become an expert in the trade. AI anything will only dig a hole for software to die in. Cheapens the product, butchers the process and absolutely decimates any hope for skill development for future junior developers. I'll just keep chugging along, with debian, python and vim, as I always ha…

sorry for the snark, but missing the forest for the trees here. unless it's just some philosophical idea, use the tools that save you time. if anything it saves you writing boilerplate or making careless errors.

i don't need to "hand write" every line and character in my code and guess what, it's still easy to understand and maintain because it's what would have written anyway. that or you're just bikeshedding minor syntax.

like if you want to be proud of a "hand built" house with hammer and nails be my guest, but don't conflate the two with always being well built.

Post reply on HN