Tinfoil 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.
> Tinfoil 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. Yeah, who puts an AI in charge of support emails with no human checks and no mention that it's an AI generated reply in the response email?
Cursor IDE support hallucinates lockout policy, causes user cancellations
101–110 of 635 posts
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#102Earlier quoted context omitted.
Yes, but humans can be held accountable.
As annoying as it is when the human support tech is wrong about something, I'm not hoping they'll lose their job as a result. I want them to have better training/docs so it doesn't happen again in the future, just like I'm sure they'll do with this AI bot.
I have empathy for humans. It's not yet a thought crime to suggest that the existence of an LLM should be ended. The analogy would make me afraid of the future if I think about it too much.
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#103Earlier quoted context omitted.
> Tinfoil 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. Yeah, who puts an AI in charge of support emails with no human checks and no mention that it's an AI generated reply in the response email?
A lot of company actually, although 100% automation is still rare.
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#104Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#105Cursor is trapped in a cat and mouse game against "hacks" where users create new accounts and get unlimited use. The repo was even trending on Github ( https://github.com/yeongpin/cursor-free-vip ). Sadly, Cursor will always be hampered by maintaining it's own VSCode fork. Others in this niche are expanding rapidly and I, myself, have started transitioning to using Roo and Cline.
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#106Cursor is weird. They have a basically unused GitHub with a thousand unanswered Issues. It's so buggy in ways that VSCode isn't. I hate it. Also I use it everyday and pay for it. That's when you know you've captured something, when people hate use your product. Any real alternatives? I've tried continue and was unimpressed with the tab completion and typing experience (felt like laggy typing on a remote server).
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#107Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#108Earlier quoted context omitted.
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.
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#109I just cancelled - not because I thought the policy change was real - but simply because this article reminded me I hadn't used it much this month.
This is where Kagi’s subscription policy comes in handy. If you don’t use it for a month, you don’t pay for it that month. There is no need to cancel it and Kagi doesn’t have to pay user acquisition costs.
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#110Earlier quoted context omitted.
> Tinfoil 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. Yeah, who puts an AI in charge of support emails with no human checks and no mention that it's an AI generated reply in the response email?
Is this sarcasm? AI has been getting used to handle support requests for years without human checks. Why would they suddenly start adding human checks when the tech is way better than it was years ago?