Earlier quoted context omitted.
Same reason they would have added checks all along. They care whether the information is correct.
These companies that can barely keep the support documentation URLs working nevermind keeping the content of their documentation up to date suddenly care about the info being correct? Have you ever dealt with customer support professionally or are you just writing what you want to be true regardless of any information to back it up?
Cursor IDE support hallucinates lockout policy, causes user cancellations
561–570 of 635 posts
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#562> Not because they made a mistake Except they did make a mistake: trusting their Simulated Intelligence (I’m done calling it “AI”.) with their customers’ trust.
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#563LLM 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…
I’m pretty much in the same boat as you, but here’s one place that LLMs helped me: In python I was scanning 1000’s of files each for thousands of keywords. A naive implementation took around 10 seconds, obviously the largest share of execution time after running instrumentation. A quick ChatGPT led me to Aho-Corasick and String searching algorithms, which I had never used before. Plug in a library and bam, 30x speed…
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#564(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…
Literally no one wants this. The entire purpose of contacting support is to get help from a human.
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#565Anything that doesn't fit the narrative must be deleted I guess.
As is so often the case, it's not the mistake itself that's the biggest problem but how people or organisations deal with the mistake.
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#566Earlier quoted context omitted.
> For context, this user’s complaint was the result of a race condition that appears on very slow internet connections. Seems like you are still blaming the user for his “very slow internet”. How do you know the user internet was slow? Couldn’t a race condition like this exist anyway with regular 2 fast internet connections competing for the same sessions? Something doesn’t add up.
huh? this is a completely reasonable and seemingly quite transparent explaination. if you want a conspiracy, there are better places to look.
Like it all sounds like a business decision (limiting 1 device to 1 sub) which is actually that was confirmed both by the actual tech limitation (logging out users from their other devices) and your own support.
Blaming the AI, then the user connection, and then some odd race conditions seem unnecessary. You can just say it was a bad business decision, roll it back, and go on with your day. Instead of treating multiple paying users badly.
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#567Earlier quoted context omitted.
> The model genuinely believes it’s giving a correct reasoning chain, but the interpretability microscope reveals it is constructing symbolic arguments backward from a conclusion. Sounds very human. It's quite common that we make a decision based on intuition, and the reasons we give are just post-hoc justification (for ourselves and others).
Isn't the point of computers to have machines that improve on default human weaknesses, not just reproduce them at scale?
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#568Earlier quoted context omitted.
> Apple made an out of character misstep by releasing a terrible UX to everyone What about Apple Maps? That roll-out was awful.
Apple had their hand forced by Google on that one afaik. Yes they knew Apple maps was bad and not up to standard yet, but they didn't really have any other choice.
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#569(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…
> We use AI-assisted responses as the first filter for email support. Literally no one wants this. The entire purpose of contacting support is to get help from a human.
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#570Earlier quoted context omitted.
The 1 million users + $200 million in revenue probably had something to do with the valuation.
Slack was a similar thing. IPO'd at 10 million users with 400M in revenue but got destroyed by Microsoft thanks to Teams. Cursor is at a worse position and at greater risk of ending up like Slack very quickly and Microsoft will do the exact same thing they did to Slack. This time by extinguishing (EEE) them by racing prices of VSCode + Copilot close to zero, until it is free. The best thing Cursor should do is for Op…