Wow, so much negativity. The Cursor team has built a wonderful product — and they made a mistake. Now haters are trying to rip it apart because of one mistake. Yeah, I also paid for the yearly plan. Yeah, I was also annoyed to get locked out on another device. Was it annoying? Yes. But will I abandon the product? No, not because of this. Chill, folks. Get a life.
Cursor IDE support hallucinates lockout policy, causes user cancellations
431–440 of 635 posts
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#432Cursor 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…
sounds like perfect grounds for a chargeback to me. Company offered a full refund via one of its Agents, company then refused to honour that offer, time to make your bank force them to refund you.
Just because you use AI for customer service doesn't mean you don't have to honour its offers to customers. Air Canada recently lost a case where its AI offered a discount to a customer but then refused to offer it "IRL"
https://www.forbes.com/sites/marisagarcia/2024/02/19/what-ai...
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#433(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…
so the actual implementation of the code to log people off was also hallucination? the enforcement too? all the way to a production environment? is this safe, or just a virtual scape goat?
To my understanding there weren't really distinct "implementation of the code to log people off" and "enforcement" - just a bug where previous sessions were being expired when a new one was created.
That an LLM then invented a reason when asked by users why they're being logged out isn't that surprising. While not impossible, I don't think there's currently indication that they intended to change policy and are just blaming it on a hallucination as a scape goat.
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#434(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…
I do truely love how you guys even went so far to hide and lock the post from Reddit. This person is not the only one to experiencing this bug. As this thread has pointed out.
I dunno, that seems pretty reasonable to me simply for stopping the spread of misinformation. The main story will absolutely get written up by some smaller news sources, but is it really a benefit for someone facing a similar issue in the future to find an outdated and probably confusing Reddit post about it?
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#435Wow, so much negativity. The Cursor team has built a wonderful product — and they made a mistake. Now haters are trying to rip it apart because of one mistake. Yeah, I also paid for the yearly plan. Yeah, I was also annoyed to get locked out on another device. Was it annoying? Yes. But will I abandon the product? No, not because of this. Chill, folks. Get a life.
Sorry but this screams copium. Its right in your face why cursor is bad, and your response is "but the product is good". Is it? What did they do better than e.g. aider, claude code and zed? What makes them stand out?
I honestly don't get it, but if you want to support such a lazy team then have at it, no one's stopping you
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#436(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…
> 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.
And what’s a customer supposed to do with that information? Know that they can’t trust it? What’s the point then?
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#437There 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.
https://www.anthropic.com/research/tracing-thoughts-language... The section about hallucinations is deeply relevant. Namely, Claude sometimes provides a plausible but incorrect chain-of-thought reasoning when its “true” computational path isn’t available. The model genuinely believes it’s giving a correct reasoning chain, but the interpretability microscope reveals it is constructing symbolic arguments backward from…
While some of what you say is an interesting thought experiment, I think the second half of this argument has, as you'd put it, a low symbolic coherence and low plausibility.
Recognizing the relevance of coherence and plausibility does not need to imply that other aspects are any less relevant. Redefining truth merely because coherence is important and sometimes misinterpreted is not at all reasonable.
Logically, a falsehood can validly be derived from assumptions when those assumptions are false. That simple reasoning step alone is sufficient to explain how a coherent-looking reasoning chain can result in incorrect conclusions. Also, there are other ways a coherent-looking reasoning chain can fail. What you're saying is just not a convincing argument that we need to redefine what truth is.
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#438(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…
> * 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. Don't use AI. Actually care. Like, take a step back, and realise you should give a shit about support for a paid product. Don't get me wrong: AI is a very effective tool, *for doing things you don't care about*. I had to do a random docker compose change the the other day. I…
There’s AI and there’s “AI”, and this whole drama would have been avoided by returning links to an FAQ rather found using embedding search rather than actually then trying to turn it into a textual answer, which — working with these systems all day — is madness
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#439There 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.
https://www.anthropic.com/research/tracing-thoughts-language... The section about hallucinations is deeply relevant. Namely, Claude sometimes provides a plausible but incorrect chain-of-thought reasoning when its “true” computational path isn’t available. The model genuinely believes it’s giving a correct reasoning chain, but the interpretability microscope reveals it is constructing symbolic arguments backward from…
> 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).
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#440Earlier 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.
Of course they had a choice: they could have stuck with google maps for longer, and they probably also could have invested more in data and UI beforehand. They could have launched a submarine non-apple-branded product to test the waters. They could likely have done other things we haven't thought of here, in this thread.
Quite plausibly they just didn't realize how rocky the start would be, or perhaps they valued that immediate strategic autonomy more in the short-term that we think, and willingly chose to take the hit to their reputation rather than wait.
Regardless, they had choices.