Live data from Hacker News

Regression: malware reminder on every read still causes subagent refusals

github.com

131–140 of 165 posts

Re: Regression: malware reminder on every read still causes subagent refusals

#131

This is a great example on why Elon is right. AI should be a tool that does the users bidding, and not a moral agent that nerfs itself to protect some arbitrary line it has.

Counterpoint: generated CSAM on his platform.

Additional counterpoint "mechahitler" chatbot. For those who have forgotten https://www.forbes.com/sites/tylerroush/2025/07/09/elon-musk...

Re: Regression: malware reminder on every read still causes subagent refusals

#132

Earlier quoted context omitted.

> You honestly think “Anthropic employees are script kiddies with inflated egos that are high on their own supply” is a reasonable stance? Maybe not the script kiddies part, but "high on their own supply" is certainly not unreasonable.

I don’t understand the hostility and insulting tones being reasonable now. The comment is not at all just saying “their usage of their own AI is causing these issues”, it’s just a lot of hostility, I don’t see the value of these kind of insults.

lol "hostility" - they sell a very high profile product and the issues seem to reflect bad engineering culture. therefore, I say their culture smells bad.

Re: Regression: malware reminder on every read still causes subagent refusals

#133

Using Claude as a malware detector is incredibly wasteful.

But it definitely makes anyhropic a lot of money!to be fair a lot of software engineers are claiming they are not reading the code claude makes anymore... So someone should probably inspect it at some point or something to make some statement about whether they are vibing with malware or whatever the youngsters are saying these days

Re: Regression: malware reminder on every read still causes subagent refusals

#134
post #4

I am still baffled by the fact that we have collectively agreed to use agentic harnesses by the same companies that are selling access to their APIs. I mean, I am sure they don't mean it but they have the incentive to burn as much tokens as they are allowed to get away with. Also for better or worse I imagine the Anthropic engineers use Claude Code on some sort of Unlimited plan that practically makes no sense for re…

They also have incentive to nerf models occasionally, so they rarely one shot the task and more often they do it wrong and then you have to spend on tokens to correct it. Bonus points if model suddenly goes completely dumb then you have to start the session over.

Factual. Watch mythos is just what opus used to be before it drifted.

Re: Regression: malware reminder on every read still causes subagent refusals

#135
post #47

Earlier quoted context omitted.

It's proof that Anthropic is high on their own supply. I've heard them described as data science script kiddies with inflated egos and it seems spot-on.

What a joke. If "Anthropic is just a bunch of script kiddies" then everyone is, considering dozens of billions pored into beating their models yet they're still the go-to for coding and have been for quite a while now. Just a nonsensical thing to say.

They got dethroned by some random Chinese company this month again. I don't think they are script kiddies but I think they have a moat on gpus.

The US is doing everything to make it so hard for other countries to compete. And yet, with everything stacked against all these other companies, and with way way less money and way less fancy researchers they get beat over and over again. Usually by companies who AI isn't even their main product.

Actually Alibaba dethroned sonnet with a model that's like 1/100th the size and can run on commodity hardware this month too. So they do look kind of silly...

Definitely not script kiddies, but the way the researchers get managed makes them look goofy and sloppy and not interested in benefitting the consumer.

Re: Regression: malware reminder on every read still causes subagent refusals

#137

Earlier quoted context omitted.

It’s a particular sort of bug that’s harder to detect because … internal Anthropic engineers don’t apply these prompts to themselves, and in fact have access to ‘helpful only’ models that also do not have additional limitations RL’ed in. (Or perhaps they’re RL’ed out - not sure of current training mechanisms.) These ‘rules for thee and not for me’ are qualitatively created and implemented, and are thus extremely hard…

They must have some sort of smoke tests for common operations, run in a test harness with the system prompts they force on users, right? ....Right? What kind of Mickey mouse operation are they running over there?

In the original claude degradation followup email Boris mentioned they are upping the percentage of engineers required to use the public version of claude code. I have no idea what percentage this is, or how much of a punishment it is considered to be. :)

That said, I was sympathetic to the recent bug reports —- to trigger one, you’d need to have a session that waited an hour doing nothing and then very specifically tested for in-context retrieval. I don’t want to run that test, do you want to run that test?

Re: Regression: malware reminder on every read still causes subagent refusals

#138
I'm currently pinning to 4.6 and the last 4.6 based CC. I apologize to all the canaries!

I think it's important for CC to also be able to make unit test code that might contain mild exploits, to test for security vulnerabilities.

The biggest complaint about vibe coding is that it's insecure. The funny part now is that if you DO try to secure it, you hit guardrails.

There is a contact form for Anthropic if you run into some of them on 4.6 at least.

Re: Regression: malware reminder on every read still causes subagent refusals

#139
post #12

> wastes user money and bricks managed agents This issue is representative of a larger problem. Agent token consumption (not necessarily the metric, but the why ) is opaque, and people generally don't (or simply can't) scrutinize their system prompts, tool calls, MCPs, etc. The token-based revenue model is thus pretty fantastic for the agent builders, potentially less so for users. I think people have been willing to…

[flagged]

Re: Regression: malware reminder on every read still causes subagent refusals

#140

Earlier quoted context omitted.

They’ve said themselves that Claude code is 100% vibe coded now. That certainly meets the criteria of “script kiddies” and “high on their own supply”. The negative connotations are there on purpose because of the bugs and issues that these products have, something which presumably they wouldn’t have if there was human oversight and acknowledgement that the AI isn’t infallible.

> They’ve said themselves that Claude code is 100% vibe coded now. That certainly meets the criteria of “script kiddies” That's not what script kiddies are at all. > The negative connotations are there on purpose because of the bugs and issues that these products have, something which presumably they wouldn’t have if there was human oversight and acknowledgement that the AI isn’t infallible. That's a big assumption,…

> That's not what script kiddies are at all.

Sure it is. The new age of script kiddies: they don’t know how to do it for themselves, but they can run a script (or tell the AI to) to do it for them.

> That's a big assumption

We can only see the results, which are more and more bugs, problems, regressions, etc. That’s not normal behavior. Yes all we can do is speculate, we don’t know the real reasons for the issues, but it’s clear there are issues and they appear to be getting worse.

Post reply on HN