Cursor IDE support hallucinates lockout policy, causes user cancellations
621–630 of 635 posts
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#622Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#623(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…
Why would anyone trust you? The best case scenario is that you lied about having people answer support. LLMs pretending to be people (you named it Sam!) and not labeled as such is clearly intended to be deceptive. Then you tried to control the narrative on reddit. So forgive me if I hit that big red DOUBT button. Even in your post you call it "AI-assisted responses" which is as weaselly as it gets. Was it a chatbot r…
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#624Earlier quoted context omitted.
> 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.
Sorta? I mean I want my problem fixed, regardless of it it's a person or not. Having a person listen to me complain about my problems might sooth my conscience, but I can't pay my bill or why was it so high; having those answered by a system that is contextualized to my problem sand is empowered to fix it, and not just a talking to a brick wall? I wouldn't say totally fine, but at the end of the day, if my problem is…
You're imagining that if you get the answer you want from the AI you hang up the phone, and if you don't you're imagining a human will pick up and have the political power and will to overrule the AI. I think it's more realistic is the way things have played out here: nobody took or had any responsibility because "they made the AI responsible" and second-guessing that choice isn't second-guessing the AI, it's second-guessing the human leaders who decreed that human support had no value. This with the result that the humans would let the AI go about as far as setting fire to the building before some kind of human element imbued with any real accountability steps in. The evidence of this is all the ignored requests presented here.
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#625Earlier quoted context omitted.
I find that if you turn off telemetry (i.e. turn on privacy) the resource hogging slows down a lot
Hmm. I double checked and I have privacy mode enabled, so I don't think that's the root cause. I also removed all but the bare essential extensions (only the theme I'm using and the core language support extensions for typescript and python).
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#626Earlier quoted context omitted.
I have a hard time being sold on “yea it’s wrong a lot, also you have to spend more time than you already do on code review.” Getting to sit down and write the code is the most enjoyable part of the job, why would I deprive myself of that? By the time the problem has been defined well enough to explain it to an LLM sitting down and writing the code is typically very simple.
The parts worth thinking about you still think about. The parts that you’ve done a million times before you delegate so you can spend better and greater effort on the parts worth thinking about.
That's where I'm confused. I've been coding for more than 20 years, and every task I ever did was different from the other ones. What kind of task do you do a million times before realizing that you should script it in bash or Python?
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#627Earlier quoted context omitted.
I have a hard time being sold on “yea it’s wrong a lot, also you have to spend more time than you already do on code review.” Getting to sit down and write the code is the most enjoyable part of the job, why would I deprive myself of that? By the time the problem has been defined well enough to explain it to an LLM sitting down and writing the code is typically very simple.
You're giving the game away when you talk about the joy LLMs are robbing from you. I think we all intuit why people don't like the idea of big parts of their jobs being automated away! But that's not an argument on the merits. Our entire field is premised on automating people's jobs away, so it's always a little rich to hear programmers kvetching about it being done to them.
Watch out, you’re giving your game away.
My job is about enabling analysis that was previously done ad hoc and informally. If I’m harming people then that’s something I have to take responsibility for, but it’s also caused not by my direct contribution but by the larger system that I’m working within.
I expressively don’t want to automate away work when that will just result in more profit for private owners and less income for regular working people.[1] And I also don’t want to automate work if that means shifting drudgery to some worker to fill in that freed up time.
And how does this contradict what “we” are doing and stand for!? We criticize technology on this board all the time!
But it’s nice to have the priorities of such a prominent member on the record.
[1] But I DO want to automate work in the hypothetical society where we all own the automation and thus the only thing we are deprived of is drudgery.
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#628Earlier quoted context omitted.
This is not the first time that Apple has released a terrible UX that very few users liked, and it certainly wont be the last. I don’t necessarily agree with the post you’re responding to, but what I will give Apple credit for is making their AI offering unobtrusive. I tried it, found it unwanted and promptly shut it off. I have not had to think about it again. Contrast that with Microsoft Windows, or Google - both s…
On Instagram, the search is now "powered by Meta AI". Cannot do anything about it.
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#629I don't understand the negativity. I use Cursor and love it. Are there real challenges with forking VS Code? Yep. Are there glitches with LLMs? Sure. Are there other AI-powered coding alternatives that can do some of the same things? You betcha. But net-net, Cursor's an amazing power tool that strongly extends what we can accomplish in any hour, day, or week.
> I don't understand the negativity. AI replied to support email, and told people a session bug was a feature.
This one failure is kitchen-sinking into a broad list of grievances, perceived slights, or unrelated problems all at once. I don't understand that, since I'm finding Cursor to be strong, helpful, and constantly improving. My experience is entirely different from this list of grievances.
Re: Cursor IDE support hallucinates lockout policy, causes user cancellations
#630Earlier quoted context omitted.
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 tha…
> They could have launched a submarine non-apple-branded product to test the waters.
This is a great idea. Are there any past Apple (or non-Apple) examples of this product release strategy?