Live data from Hacker News

Cursor IDE support hallucinates lockout policy, causes user cancellations

old.reddit.com

121–130 of 635 posts

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

#121
post #31

Cursor 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).

Cursor + Vim plugin never worked for me, so I switched back to Nvim and never looked back. Nvim already has: avante, codeCompanion, copilot, and many other tools + MCP + aider if you're into that.

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

#122
post #55
post #31

Cursor 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).

VS Code with standard copilot for tab completion and Aider in a terminal window for all the heavier lifts, asking questions, architecting etc. And it’s cheap! I’ve been using it with OpenRouter (lets you easily switch models and providers) and my $10 of credits lasted weeks. Granted, I also use Claude a lot in the browser.

The reason many prefer Cursor over VSCode + GitHub Copilot is because of how much faster Cursor is for tab completion. They use some smaller models that are latency optimized specifically to make the tab completion feel as fast as possible.

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

#123
post #39

This 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…

It's a Reddit post with 65 upvotes. Where are people getting millions of dollars overnight? HN is too dramatic lol

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

#124
post #12

Earlier 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?

AI may have been used to pick from a repertoire of stock responses, but not to generate (hallucinate) responses. Thus you may have gotten a response that fails to address your request, but not a response with false information.

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

#125
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 have. No LLM, no LSP, heck not even autocompletion. But damn proud of every hand crafted, easy to maintain and fully understood line of code I'll write.

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

#127
post #79

Earlier quoted context omitted.

First of all, their docs link to the market place of ms: https://www.cursor.com/how-to-install-extension Which is basically an article to use an extension in a way that’s basically forbidden use. If that was not bad enough the editor also told you to install certain extensions if certain file extensions were used that were also against the tos of the extension. And basically cursor can just be using the vsix marketpl…

I don't see a problem with this. If it's an extension on my machine, why do I care about the TOS?

The extensions themselves have licenses that prohibit their use with anything other than VSCode.

(You should keep this in mind next time someone tells you that VSCode is "open source", by the way. The core IDE is, sure, but if you need to do e.g. Python or C++, the official Microsoft extensions involved all have these kinds of clauses in them.)

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

#128
post #41

I 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.

Slack does this as well. It's a genius idea from a business perspective. Normally IT admins have to go around asking users if they need the service (or more likely you have to request a license for yourself), regularly monitor usage, deactivate stale users etc., all to make sure the company isn't wasting money. Slack comes along and says - don't worry, just onboard every user at the company. If they don't log in and send at least N messages we won't bill them for that month.

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

#129
post #43

Earlier quoted context omitted.

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.

That only works well if someone is in an appropriate job though. Keeping someone in a position they are unqualified for and majorly screwing up at isn't doing anyone any favors.

Fully agree. My analogy fits here too.

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

#130
post #31

Cursor 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).

Any competing product has to absolutely nail tab autocomplete like Cursor has. It's super fast, very smart (even guessing across modules) and very often correct.
Post reply on HN