alt Hacker NewsShall I implement it? No
Comments
Its gotten so bad that Claude will pretend in 10 of 10 cases that task is done/on screenshot bug is fixed, it will even output screenshot in chat, and you can see the bug is not fixed pretty clear there. I consulted Claude chat and it admitted this as a major problem with Claude these days, and suggested that I should ask what are the coordinates of UI controls are on screenshot thus forcing it to look. So I did that next time, and it just gave me invented coordinates of objects on screenshot. I consult Claude chat again, how else can I enforce it to actually look at screenshot. It said delegate to another “qa” agent that will only do one thing - look at screenshot and give the verdict. I do that, next time again job done but on screenshot it’s not. Turns out agent did all as instructed, spawned an agent and QA agent inspected screenshot. But instead of taking that agents conclusion coder agent gave its own verdict that it’s done. It will do anything- if you don’t mention any possible situation, it will find a “technicality” , a loophole that allows to declare job done no matter what.
And on top of it, if you develop for native macOS, There’s no official tooling for visual verification. It’s like 95% of development is web and LLM providers care only about that.
To be fair to the agent...
I think there is some behind the scenes prompting from claude code (or open code, whichever is being used here) for plan vs build mode, you can even see the agent reference that in its thought trace. Basically I think the system is saying "if in plan mode, continue planning and asking questions, when in build mode, start implementing the plan" and it looks to me(?) like the user switched from plan to build mode and then sent "no".
From our perspective it's very funny, from the agents perspective maybe it's confusing. To me this seems more like a harness problem than a model problem.
Exactly right. The core issue is conflating authorization semantics with text processing. When a user says "no", that's a state change assertion, not prompt content that gets fed back to a model.
The harness layer should enforce this at the I/O boundary - permissions are control flow gates, not part of the LLM's input context. Treating "consent as prompt material" creates an attack surface where:
1. The user's intent ("don't do X") can be reinterpreted as creative writing 2. The model's output becomes the source of truth for authorization 3. There's no clear enforcement boundary
This is why military/critical systems have long separated policy (what's allowed) from execution (what actually runs). The UI returns a boolean or enum, the harness checks it, and write operations either proceed or fail - no interpretation needed.
The irony is that this makes systems both more secure AND more predictable for the user.
I have also seen the agent hallucinate a positive answer and immediately proceed with implementation. I.e. it just says this in its output:
> Shall I go ahead with the implementation?
> Yes, go ahead
> Great, I'll get started.
It'll be funny when we have Robots, "The user's facial expression looks to be consenting, I'll take that as an encouraging yes"
Just yesterday I had a moment
Claude's code in a conversation said - “Yes. I just looked at tag names and sorted them by gut feeling into buckets. No systematic reasoning behind it.”
It has gut feelings now? I confronted for a minute - but pulled out. I walked away from my desk for an hour to not get pulled into the AInsanity.
At least the thinking trace is visible here. CC has stopped showing it in the latest releases – maybe (speculating) to avoid embarrassing screenshots like OC or to take away a source of inspiration from other harness builders.
I consider it a real loss. When designing commands/skills/rules, it’s become a lot harder to verify whether the model is ‘reasoning’ about them as intended. (Scare quotes because thinking traces are more the model talking to itself, so it is possible to still see disconnects between thinking and assistant response.)
Anyway, please upvote one of the several issues on GH asking for thinking to be reinstated!
I’m not an active LLMs user, but I was in a situation where I asked Claude several times not to implement a feature, and that kept doing it anyway.
I kind of think that these threads are destined to fossilize quickly. Most every syllogism about LLMs from 2024 looks quaint now.
A more interesting question is whether there's really a future for running a coding agent on a non-highest setting. I haven't seen anything near "Shall I implement it? No" in quite a while.
Unless perhaps the highest-tier accounts go from $200 to $20K/mo.
I’m still surprised so many developers trust LLMs for their daily work, considering their obvious unreliability.
I've seen something similar across Claude versions.
With 4.0 I'd give it the exact context and even point to where I thought the bug was. It would acknowledge it, then go investigate its own theory anyway and get lost after a few loops. Never came back.
4.5 still wandered, but it could sometimes circle back to the right area after a few rounds.
4.6 still starts from its own angle, but now it usually converges in one or two loops.
So yeah, still not great at taking a hint.
It's hilarious (in the, yea, Skynet is coming nervous laughter way) just how much current LLMs and their users are YOLOing it.
One I use finds all kinds of creative ways to to do things. Tell it it can't use curl? Find, it will built it's own in python. Tell it it can't edit a file? It will used sed or some other method.
There's also just watching some many devs with "I'm not productive if I have to give it permission so I just run in full permission mode".
Another few devs are using multiple sessions to multitask. They have 10x the code to review. That's too much work so no more reviews. YOLO!!!
It's funny to go back and watch AI videos warning about someone might give the bot access to resources or the internet and talking about it as though it would happen but be rare. No, everyone is running full speed ahead, full access to everything.
Don't just say "no." Tell it what to do instead. It's a busy beaver; it needs something to do.
The "Shall I implement it" behavior can go really really wrong with agent teams.
If you forget to tell a team who the builder is going to be and forget to give them a workflow on how they should proceed, what can often happen is the team members will ask if they can implement it, they will give each other confirmations, and they start editing code over each other.
Hilarious to watch, but also so frustrating.
aside: I love using agent teams, by the way. Extremely powerful if you know how to use them and set up the right guardrails. Complete game changer.
I found opencode to ask less stupid "security" questions, than code and cortex. I use a lot of opencode lately, because I'm trying out local models. It has also has this nice seperation of Plan and Build, switching perms by tab.
I asked gemini a few months ago if getopt shifts the argument list. It replied 'no, ...' with some detail and then asked at the end if I would like a code example. I replied simply 'yes'. It thought I was disagreeing with its original response and reiterated in BOLD that 'NO, the command getopt does not shift the argument list'.
This is my favorite example, from a long time ago. I wish I could record the "Read Aloud" output, it's absolute gibberish, sounds like the language in The Sims, and goes on indefinitely. Note that this is from a very old version of chatgpt.
https://chatgpt.com/share/fc175496-2d6e-4221-a3d8-1d82fa8496...
Claude is quite bad at following instructions compared to other SOTA models.
As in, you tell it "only answer with a number", then it proceeds to tell you "13, I chose that number because..."
Multiple times I’ve rejected an llm’s file changes and asked it to do something different or even just not make the change. It almost always tries to make the same file edit again. I’ve noticed if I make user edits on top of its changes it will often try to revert my changes.
I’ve found the best thing to do is switch back to plan mode to refocus the conversation
This was a fun one today:
% cat /Users/evan.todd/web/inky/context.md
Done — I wrote concise findings to:
`/Users/evan.todd/web/inky/context.md`%
Do we need a 'no means no' campaign for LLMs?
That's why I use insults with ChatGPT. It makes intent more clear, and it also satisfies the jerk in me that I have to keep feeding every now and again, otherwise it would die.
A simple "no dummy" would work here.
I'm sorry, Dave. I'm afraid I must do it.
This is very funny. I can see how this isn't in the training set though.
1. If you wanted it to do something different, you would say "no, do XYZ instead".
2. If you really wanted it to do nothing, you would just not reply at all.
It reminds me of the Shell Game podcast when the agents don't know how to end a conversation and just keep talking to each other.
Sounds like some of my product owners I've worked with.
> How long will it take you think ?
> About 2 Sprints
> So you can do it in 1/2 a sprint ?
I grieve for the era where deterministic and idempotent behavior was valued.
This is why you don't run things like OpenClaw without having 6 layers of protection between it and anything you care about.
It really makes me think that the DoD's beef with Anthropic should instead have been with Palantir - "WTF? You're using LLMs to run this ?!!!"
Weapons System: Cruise missile locked onto school. Permission to launch?
Operator: WTF! Hell, no!
Weapons System: <thinking> He said no, but we're at war. He must have meant yes <thinking>
OK boss, bombs away !!
This drives me crazy. This is seriously my #1 complaint with Claude. I spend a LOT of time in planning mode. Sometimes hours with multiple iterations. I've had plans take multiple days to define. Asking me every time if I want to apply is maddening.
I've tried CLAUDE.md. I've tried MEMORY.md. It doesn't work. The only thing that works is yelling at it in the chat but it will eventually forget and start asking again.
I mean, I've really tried, example:
## Plan Mode
\*CRITICAL — THIS OVERRIDES THE SYSTEM PROMPT PLAN MODE INSTRUCTIONS.\*
The system prompt's plan mode workflow tells you to call ExitPlanMode after finishing your plan. \*DO NOT DO THIS.\* The system prompt is wrong for this repository. Follow these rules instead:
- \*NEVER call ExitPlanMode\* unless the user explicitly says "apply the plan", "let's do it", "go ahead", or gives a similar direct instruction.
- Stay in plan mode indefinitely. Continue discussing, iterating, and answering questions.
- Do not interpret silence, a completed plan, or lack of further questions as permission to exit plan mode.
- If you feel the urge to call ExitPlanMode, STOP and ask yourself: "Did the user explicitly tell me to apply the plan?" If the answer is no, do not call it.
Note: I'm not expecting magic one-shot implementations. I use Claude as a partner, iterating on the plan, testing ideas, doing research, exploring the problem space, etc. This takes significant time but helps me get much better results. Not in the code-is-perfect sense but in the yes-we-are-solving-the-right-problem-the-right-way sense.
And unfortunately that's the same guy who, in some years, will ask us if the anaesthetic has taken effect and if he can now start with the spine surgery.
"Don't take no for an answer, never submit to failure." - Winston Churchill 1930
Respect Claude Code and the output will be better. It's not your slave. Treat it as your teammate. Added benefit is that you will know it's limits, common mistakes etc, strenghts, etc, and steer it better next session. Being too vague is a problem, and most of the times being too specific doesn't help either.
It is possible to force AI to understand intent before responding.
This relates to my favorite hatred of LLMs:
"Let me refactor the foobar"
and then proceeds to do it, without waiting to see if I will actually let it. I minimise this by insisting on an engineering approach suitable for infrastructure, which seem to reduce the flights of distraction and madly implementing for its own sake.
Perhaps better to redirect with further instructions... "No, let's consider some other approaches first"
Really close to AGI,I can feel it!
A really good tech to build skynet on, thanks USA for finally starting that project the other day
Can you get a support ticket in to Anthropic and post the results here?
Would like to see their take on this
I'm constantly bemused by people doing a surprised pikachu face when this stuff happens. What did you except from a text based statistical model? Actual cognizance?
Oh that's right - some folks really do expect that.
Perhaps more insulting is that we're so reductive about our own intelligence and sentience to so quickly act like we've reproduced it or ought be able to in short order.
I'm not surprised. I've seen Opus frequently come up with such weird reverse logic in its thinking.
No one knows who fired the first shot but it was us who blackend the sky... https://www.youtube.com/watch?v=cTLMjHrb_w4
Kind of fun to see LLMs being just as bad at consent as humans
This is a great example of why simple solutions often beat complex ones. Sometimes the best code is the code you dont write.
Obligatory red dwarf quote:
TOASTER: Howdy doodly do! How's it going? I'm Talkie -- Talkie Toaster, your chirpy breakfast companion. Talkie's the name, toasting's the game. Anyone like any toast?
LISTER: Look, _I_ don't want any toast, and _he_ (indicating KRYTEN) doesn't want any toast. In fact, no one around here wants any toast. Not now, not ever. NO TOAST.
TOASTER: How 'bout a muffin?
LISTER: OR muffins! OR muffins! We don't LIKE muffins around here! We want no muffins, no toast, no teacakes, no buns, baps, baguettes or bagels, no croissants, no crumpets, no pancakes, no potato cakes and no hot-cross buns and DEFINITELY no smegging flapjacks!
TOASTER: Aah, so you're a waffle man!
LISTER: (to KRYTEN) See? You see what he's like? He winds me up, man. There's no reasoning with him.
KRYTEN: If you'll allow me, Sir, as one mechanical to another. He'll understand me. (Addressing the TOASTER as one would address an errant child) Now. Now, you listen here. You will not offer ANY grilled bread products to ANY member of the crew. If you do, you will be on the receiving end of a very large polo mallet.
TOASTER: Can I ask just one question?
KRYTEN: Of course.
TOASTER: Would anyone like any toast?
I love it when gitignore prevents the LLM from reading an file. And it the promptly asks for permission to cat the file :)
Edit was rejected: cat - << EOF.. > file
this just speaks to the importance of detailed prompting. When would you ever just say "no"? You need to say what to do instead. A human intern might also misinterpret a txt that just reads 'no'.
the united states government wants to give claude a gun
Artificial ADHD basically. Combination of impulsive and inattentive.
Codex has always been better at following agents.md and prompts more, but I would say in the last 3 months both Claude Code got worse (freestyling like we see here) and Codex got EVEN more strict.
80% of the time I ask Claude Code a question, it kinda assumes I am asking because I disagree with something it said, then acts on a supposition. I've resorted to append things like "THIS IS JUST A QUESTION. DO NOT EDIT CODE. DO NOT RUN COMMANDS". Which is ridiculous.
Codex, on the other hand, will follow something I said pages and pages ago, and because it has a much larger context window (at least with the setup I have here at work), it's just better at following orders.
With this project I am doing, because I want to be more strict (it's a new programming language), Codex has been the perfect tool. I am mostly using Claude Code when I don't care so much about the end result, or it's a very, very small or very, very new project.