I do a few AI projects and my number one rule is to use LLMs only to process requests and never to generate responses.
Cursor IDE support hallucinates lockout policy, causes user cancellations
61–70 of 635 posts
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#62AI bubble popping yet? Looking forward to not buying GPUs that cost $2K (before tariffs…).
1) there is no AI bubble, it has revolutionized how we communicate and learn
2) you don't need to buy an expensive GPU for local LLM, any contemporary laptop with enough RAM is sufficient to run an uncensored Gemma-3 fast
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#63There 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.
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#64Tinfoil hat me says that it was a policy change that they are blaming on an "AI Support Agent" and hoping nobody pokes too much behind the curtain. Note that I have absolutely no knowledge or reason to believe this other than general distrust of companies.
Given how incredibly stingy tech companies are about spending any money on support, I would not be surprised if the story about it being a rogue AI support agent is 100% true.
It also seems like a weird thing to lie about, since it's just another very public example of AI fucking up something royally, coming from a company whose whole business model is selling AI.
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#65From cursor developer: "Hey! We have no such policy. You're of course free to use Cursor on multiple machines. Unfortunately, this is an incorrect response from a front-line AI support bot. We did roll out a change to improve the security of sessions, and we're investigating to see if it caused any problems with session invalidation. We also do provide a UI for seeing active sessions at cursor.com/settings. Apologies…
lol this is totally the kind of company you should be giving money too
and the best thing about it is that the base model is going to be trained on reddit posts so expect SupportBot3000 to be even more confident about this fact in the future!
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#66This is "AGI's finest". It's what we all wanted. Replacing your human support team to be run exclusively by AI LLM bots whilst they hallucinate to their users. All unchecked. Now this bug has now turned into a multi-million dollar mistake and costed Cursor to lose millions of dollars overnight. What if this was a critical control system in a hospital or energy company and their AI support team (with zero humans) hall…
Are we sure that the damage is in “millions”? Could it not be just the same old “vocal and loud minority”, who will wake up tomorrow and re-activate their subscription before the lunch break once Cursor team comes and writes a heartfelt apology post (well generated by AI with a system prompt of “you are a world class PR campaign manager …”)?
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#67AI bubble popping yet? Looking forward to not buying GPUs that cost $2K (before tariffs…).
1) there is no AI bubble, it has revolutionized how we communicate and learn 2) you don't need to buy an expensive GPU for local LLM, any contemporary laptop with enough RAM is sufficient to run an uncensored Gemma-3 fast
I'm an AI fan, but there's clearly a desperate attempt by just about every tech company to integrate AI at the cost of genuinely productive developments in the space, in a manner that one might describe as a "bubble." Microsoft's gotta buy enough GPUs to handle Copilot in Windows Notepad, after all...
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#68This is "AGI's finest". It's what we all wanted. Replacing your human support team to be run exclusively by AI LLM bots whilst they hallucinate to their users. All unchecked. Now this bug has now turned into a multi-million dollar mistake and costed Cursor to lose millions of dollars overnight. What if this was a critical control system in a hospital or energy company and their AI support team (with zero humans) hall…
You're right, but this is more general - it has nothing to do with AGI and everything to do with poor management. It reminds me very much of the Chernobyl disaster, and the myriad examples in Taleb's "The Black Swan".
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#69Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#70Earlier 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…
Wait, what?! Slack got destroyed by Teams? You seem to be living a few parallel universes away from the one I'm in.