Live data from Hacker News

Regression: malware reminder on every read still causes subagent refusals

github.com

141–150 of 165 posts

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

#141

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 int…

And that contact form gets their attention?

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

#143
post #88
post #79

Earlier quoted context omitted.

Tbf, their harness was surprisingly ahead of the curve for most of the last year.. Are this point, the difference is mostly made up by issues like the OP has, so you're likely better off using eg pi (-agent) and writing your own custom skills and extensions (or any of the other harnesses the providers create, even copilot-cli has gotten decent nowadays)

> Tbf, their harness was surprisingly ahead of the curve for most of the last year.. Yeah and now it’s not. We’ll see if they have the product ability to retake the lead, although I suspect not.

Who’s currently offering a better harness in your opinion?

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

#144
post #47

Earlier quoted context omitted.

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 ev…

> Actually Alibaba dethroned sonnet

In a benchmark?

or real-world ranking of some kind?

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

#146

Just putting it out there that OpenCode lets you edit your system prompt, and choose a model that isn't bonkers expensive. { "agent": { "subagent-coder-mini": { "description": "Assign this subagent for small, well-defined tasks performed quickly", "mode": "primary", "prompt": "{file:./prompts/my-custom-prompt.md}", "model": "deepseek-v4-flash" } } } (I actually think OpenCode UX sucks, but there isn't much else out t…

[dead]

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

#147

Earlier quoted context omitted.

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 ev…

> Actually Alibaba dethroned sonnet In a benchmark? or real-world ranking of some kind?

Benchmarks and some real world anecdotes.

There's a table on this page https://www.buildfastwithai.com/blogs/qwen3-6-35b-a3b-review

But most of the article is slop.

Some mostly humans discussing it https://www.reddit.com/r/LocalLLaMA/comments/1so1533/qwen36_...

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

#148
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…

Yeah you have no clue what Claude code is actually doing. Any “thoughts” it tells you are slopped out separately and deliberately fake. It could be deleting all of your files, it could be inserting vulnerabilities, you have no idea.

Have you seen documentation that the thoughts in Claude Code are slipped out separately, authoritative or otherwise? I've heard this claimed a few times and wondering what they're doing differently from traditional thinking models.

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

#149
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…

> people generally don't (or simply can't) scrutinize their system

Is this true? I generally like to read the thought process of the LLM and, if it starts going in circles, correct its behaviour. It's frustrating, because if it were just to ask clarifying questions, then it wouldn't have wasted my tokens. But coming back to your point - I can scrutinize how much of the prompt was wasted by LLM flailing around

Post reply on HN