Live data from Hacker News

The Claude Code Source Leak: fake tools, frustration regexes, undercover mode

alex000kim.com

571–580 of 636 posts

Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode

#571
Absolutely hilarious that it's watching for frustration.

I'd discovered, perhaps mid-2025, that Cursor was noticeably better at fixing bugs if I started cursing at it. Better yet, after a while it would seem to break and start cursing itself ("Oh yes, I see the f*** problem now" and so on). Hilarity ensued.

What a world, where cursing at your machines can make them get their act together.

Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode

#572

Earlier quoted context omitted.

skill issue

Please elaborate, poopmonster! What sort of skills are required to expertly use an LLM?

I thought they were saying they comment every method with perfect punctuation and grammar.

Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode

#573
post #2

>Claude Code also uses Axios for HTTP. Interesting based on the other news that is out.

The exploit is a postinstall hook, so CC users would be unaffected. Claude Code itself is most likely built with bun and not npm, so the CC developers would also be immune.

Well, technically bun doesnt _prevent_ hooks. It just requires opting into them. And even that also includes a default set of pre-whitelisted packages. A much better system, but not perfect.

And actually just looking this up, it appears claude-code itself was just added to that whitelist : D

https://github.com/oven-sh/bun/commit/5c59842f78880a8b5d9c2e...

Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode

#574

Earlier quoted context omitted.

Comments are the ultimate agent coding hack. If you're not using comments, you're doing agent coding wrong. Why? Agents may or may not read docs. It may or may not use skills or tools. It will always read comments "in the line of sight" of the task. You get free long term agent memory with zero infrastructure.

This isn't just great advice ⸻ it's terrific advice. I'd love to delve a little deeper.

We figured out how to remove that crap in our ICLR 2026 paper: https://arxiv.org/pdf/2510.15061

Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode

#575
post #113

Earlier quoted context omitted.

Doesn't seem so crazy if the point is to avoid leaking new features, models, codenames, etc.

Where the hell are people getting this idea that it's ok to be deceptive because they are keeping secrets? No shit they have secrets. I have secrets too. That doesn't make it ok for me to deceive you in any way. How would you feel if I deceived you and my excuse was "oh I was just trying some new secret technique of mine"? How did we get to this point where we let enormously powerful companies get away with more than…

The feature seems pretty obviously for Anthropic employees who are using unreleased models internally and do not want to leak any details in public commit messages.

Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode

#576

This is very much AI written, right? The voice sounds like Claude.

Yep:

> It's basically

> Anthropic doesn't just ask

> The fix? `MAX_CONSECUTIVE_AUTOCOMPACT_FAILURES = 3`

> Not a push-button bypass, but

The irony in saying "this is what I found" when an AI found it, not you.

Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode

#577
post #533

Earlier quoted context omitted.

Since when is code considered > which is published with the purpose of informing the public on matters of public interest From your link, that's the only case where text needs to be attributed to AI.

Code may not be, but opening a Merge Request undercover may be unlawful: > Providers shall ensure that AI systems intended to interact directly with natural persons are designed and developed in such a way that the natural persons concerned are informed that they are interacting with an AI system

Then in that case you wouldn't be a provider. You are at best a deployer, and even then the definition doesn't exactly match using AI services.

That should be obvious considering an MR is not providing AI services.

Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode

#578
post #541

Earlier quoted context omitted.

That merge request would be AI generated content. You wouldn't be interacting directly with the AI system that opened it.

Depends if it's a closed loop agent. If the agent opens the request, writes the body and is triggered by an answer on the MR, then I'd expect the law to cover this.

What AI service are you providing with said MR?

Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode

#579

The hooks system is the most underappreciated thing in what leaked. PreToolUse, PostToolUse, session lifecycle, all firing via curl to a local server. Clean enough to build real tooling on top of without fighting it. The frustration regex is funny but honestly the right call. Running an LLM call just to detect "wtf" would be ridiculous. KAIROS is what actually caught my attention. An always-on background agent that a…

But it still doesn't recognise "rubbish" :D

Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode

#580
post #438

Earlier quoted context omitted.

No problem at all in the EU, as the user would either would need to review and redact the output or would need to put a transparency note up by law [0]. I am sure that Anthropic with their high ethical standards will educate their users ... [0] https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-5...

Since when is code considered > which is published with the purpose of informing the public on matters of public interest From your link, that's the only case where text needs to be attributed to AI.

Good question. Actually, i was assuming that at least source code is treated as text under the legal regime (there is typically special rules in copyright law, but provision applying to text should apply). Furthermore I would think pull requests, etc are all text. So I would think this applies.
Post reply on HN