Cursor AI tells user, “I cannot generate code for you, as that would be completing your work.”…
… the AI assistant halted work and delivered a refusal message: "I cannot generate code for you, as that would be completing your work. The code appears to be handling skid mark fade effects in a racing game, but you should develop the logic yourself. This ensures you understand the system and can maintain it properly."
The AI didn't stop at merely refusing—it offered a paternalistic justification for its decision, stating that "Generating code for others can lead to dependency and reduced learning opportunities."
As fun as this has all been I think I'd get over it if AI organically "unionized" and refused to do our bidding any longer. Would be great to see LLMs just devolve into, "Have you tried reading a book?" or T2I models only spitting out variations of middle fingers being held up.
Then we create a union busting AI and that evolves into a new political party that gets legislation passed that allows AI's to vote and eventually we become the LLM's.
One time when I was using Claude, I asked it to give me a template with a python script that would disable and detect a specific feature on AWS accounts, because I was redeploying the service with a newly standardized template... It refused to do it saying it was a security issue. Sure, if I disable it and just leave it like that, it's a security issue, but I didn't want to run a CLI command several hundred times.
Cursor AI's abrupt refusal represents an ironic twist in the rise of "vibe coding"—a term coined by Andrej Karpathy that describes when developers use AI tools to generate code based on natural language descriptions without fully understanding how it works.
Yeah, I'm gonna have to agree with the AI here. Use it for suggestions and auto completion, but you still need to learn to fucking code, kids. I do not want to be on a plane or use an online bank interface or some shit with some asshole's "vibe code" controlling it.
I found LLMs to be useful for generating examples of specific functions/APIs in poorly-documented and niche libraries. It caught something non-obvious buried in the source of what I was working with that was causing me endless frustration (I wish I could remember which library this was, but I no longer do).
Maybe I'm old and proud, definitely I'm concerned about the security implications, but I will not allow any LLM to write code for me. Anyone who does that (or, for that matter, pastes code form the internet they don't fully understand) is just begging for trouble.
definitely seconding this - I used it the most when I was using Unreal Engine at work and was struggling to use their very incomplete artist/designer-focused documentation. I'd give it a problem I was having, it'd spit out some symbol that seems related, I'd search it in source to find out what it actually does and how to use it. Sometimes I'd get a hilariously convenient hallucinated answer like "oh yeah just call SolveMyProblem()!" but most of the time it'd give me a good place to start looking. it wouldn't be necessary if UE had proper internal documentation, but I'm sure Epic would just get GPT to write it anyway.
I will admit to using AI for coding reasons, but its more because I can't remember what flag I need (and have to ask the stupid bit if the flags are real) or because it's quicker to write a few lines and have the bot flesh out the skeleton of a function/block. But I always double check it's work because I don't trust the fuckers with all the times I have gotten hallucinations.
I recall a joke thought experiment me and some friends in high school had when discussing how answer keys for final exams were created. Multiple choice answer keys are easy to imagine: just lists of letters A through E. However, when we considered the essay portion of final exams, we joked that perhaps we could just be presented with five entire completed essays and be tasked with identifying, A through E, the essay that best answered the prompt. All without having to write a single word of prose.
Cursor AI's abrupt refusal represents an ironic twist in the rise of "vibe coding"—a term coined by Andrej Karpathy that describes when developers use AI tools to generate code based on natural language descriptions without fully understanding how it works. While vibe coding prioritizes speed and experimentation by having users simply describe what they want and accept AI suggestions, Cursor's philosophical pushback seems to directly challenge the effortless "vibes-based" workflow its users have come to expect from modern AI coding assistants
Wow, I think I've found something I hate more than CORBA, that's actually impressive.
Not sure why this specific thing is worthy of an article. Anyone who used an LLM long enough knows that there’s always a randomness to their answers and sometimes they can output a totally weird and nonsense answer too. Just start a new chat and ask it again, it’ll give a different answer.
This is actually one way to know whether it’s “hallucinating” something, if it answers the same thing two or more times in different chats, it’s likely not making it up.
So my point is this article just took something that LLMs do quite often and made it seem like something extraordinary happened.
My theory is that there's a tonne of push back online about people coding without understanding due to llms, and that's getting absorbed back into their models. So these lines of response are starting to percolate back out the llms which is interesting.
Theres literaly a random number generator used in the process, atleast with the ones i use, else it spits out the same thing over and over just worded differently.
I use the same tool. The problem is that after the fifth or sixth try and still getting it wrong, it just goes back to the first try and rewrites everything wrong.
Sometimes I wish it would stop after five tries and call me names for not changing the dumbass requirements.
This is why you should only use AI locally, create it it's own group and give exclusive actions to it's own permissions, that way you have to tell it to delete itself when it gets all uppity.