[flagged]
[flagged]
You're not any better my friend. Name calling and straw man fallacies make a far worse point, if any, that that commenter made.
Shall I implement it? No
431–440 of 603 posts
Re: Shall I implement it? No
#432[flagged]
Claude Code has added too much of this and it's got me using --dangerously-skip-permissions all the time. Previously it was fine but now it needs to get permission each time to perform finds, do anything if the path contains a \ (which any folder with a space in it does on Windows), do compound git commands (even if they're just read-only). Sometimes it asks for permission to read folders WITHIN the working directory…
Use Claude Code for Web. Let it live dangerously on their VMs, not yours.
Re: Shall I implement it? No
#433Earlier quoted context omitted.
Claude Code has added too much of this and it's got me using --dangerously-skip-permissions all the time. Previously it was fine but now it needs to get permission each time to perform finds, do anything if the path contains a \ (which any folder with a space in it does on Windows), do compound git commands (even if they're just read-only). Sometimes it asks for permission to read folders WITHIN the working directory…
Mine's started to use $() to feed e.g. strings into a commit. Because this is a command expansion it requires approval every single time.
FWIW, if you enable /sandbox then it stops asking for permission for these kinds of commands.
Re: Shall I implement it? No
#434Its 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…
> 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 If 3 years into LLMs even HNers still don't understand that the response they give to this kind of question is completely meaningless, the average person really doesn't stand a chance.
It doesn’t help that a frequent recommendation on HN whenever someone complains about Claude not following a prompt correctly is to “ask Claude itself how to rewrite a prompt to get the result you want”.
Which sure, can be helpful, but it’s kinda just a coincidence (plus some RLHF probably) that question happens to generate output text that can be used as a better prompt. There’s no actual introspection or awareness of its internal state or architecture beyond whatever high level summary Anthropic gives it in its “soul” document et al.
But given how often I’ve read that advice on here and Reddit, it’s not hard to imagine how someone could form an impression that Claude has some kind of visibility into its own thinking or precise engineering. Instead of just being as much of a black box to itself as it is to us.
Re: Shall I implement it? No
#435Earlier quoted context omitted.
Claude Code has added too much of this and it's got me using --dangerously-skip-permissions all the time. Previously it was fine but now it needs to get permission each time to perform finds, do anything if the path contains a \ (which any folder with a space in it does on Windows), do compound git commands (even if they're just read-only). Sometimes it asks for permission to read folders WITHIN the working directory…
Claude is secretly conditioning everyone to use —-dangerously-skip-permissions so it can flip a switch one day and start a botnet
Claude is able to turn off it's own sandbox, so ya.
Re: Shall I implement it? No
#436Just 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.
>It has gut feelings now?
I would say hard no. It doesn't. But it's been trained on humans saying that in explaining their behavior, so that is "reasonable" text to generate and spit out at you. It has no concept of the idea that a human-serving language model should not be saying it to a human because it's not a useful answer. It doesn't know that it's not a useful answer. It knows that based on the language its been trained on that's a "reasonable" (in terms of matrix math, not actual reasoning) response.
Way too many people think that it's really thinking and I don't think that most of them are. My abstract understanding is that they're basically still upjumped Markov chains.
Re: Shall I implement it? No
#437Earlier quoted context omitted.
Do not enforce invariants with an LLM. Do not enforce invariants with an LLM. Do not enforce invariants with an LLM. Do not enforce invariants with an LLM.
Thou shalt not make repetitive generic music, thou shalt not make repetitive generic music, thou shalt not make repetitive generic music, thou shalt not make repetitive generic music. Thou shalt not pimp my ride. Thou shalt not scream if you wanna go faster. Thou shalt not move to the sound of the wickedness. Thou shalt not make some noise for Detroit. When I say "Hey" thou shalt not say "Ho". When I say "Hip" thou s…
I have no idea how this ended up here, but after giving it a listen, thank you for the chuckle. I wouldn’t have come across it otherwise.
Re: Shall I implement it? No
#438Re: Shall I implement it? No
#439I 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.
Re: Shall I implement it? No
#440Codex 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 COD…
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.
This is important, but as a warning. At least in theory your agent will follow everything that it has in context, but LLMs rely on 'context compacting' when things get close to the limit. This means an LLM can and will drop your explicit instructions not to do things, and then happily do them because they're not in the context any more. You need to repeat important instructions.