Earlier quoted context omitted.
It’s also pretty damn obvious when LLMs write code. Nobody out here commenting every method in perfect punctuation and grammar.
skill issue
Commenting every method, how pedestrian! I comment every letter of my code!
The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
471–480 of 636 posts
Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#472>This was the most-discussed finding in the HN thread. The general reaction: an LLM company using regexes for sentiment analysis is peak irony. >Is it ironic? Sure. Is it also probably faster and cheaper than running an LLM inference just to figure out if a user is swearing at the tool? Also yes. Sometimes a regex is the right tool. I'm reading an LLM written write up on an LLM tool that just summarizes HN comments.…
Today, on "how did I get here?"
Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#473> “Do not rubber-stamp weak work” and “You must understand findings before directing follow-up work. Never hand off understanding to another worker.” :-D
You can see exactly on which humanity it q
Was trained on ;)
Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#474The Claude Code leak suggests multi-agent orchestration is largely driven by prompts (e.g., “do not rubber-stamp weak work”), with code handling execution rather than enforcing decisions.
Prompts are not hard constraints—they can be interpreted, deprioritized, or reasoned around, especially as models become more capable.
From what’s visible, there’s no clear evidence of structural governance like voting systems, hard thresholds, or mandatory human escalation. That means control appears to be policy (prompts), not enforcement (code).
This raises the core issue: If governance is “prompts all the way down,” it’s not true governance—it’s guidance.
And as model capability increases, that kind of governance doesn’t get stronger—it becomes easier to bypass without structural constraints.
Has anyone actually implemented structural governance for agent swarms — voting logic, hard thresholds, REQUIRES_HUMAN as architecture not instruction?
Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#475Earlier quoted context omitted.
I cannot bring myself to care about distillation, when these companies have built their empires on top of everyone else's stolen data, while at the same time telling the world they're out to replace us all.
Sure, AI progress comes to a halt then as everyone switches to the copycats that can't innovate, and the frontier companies are bled dry.
Qwen are the only guys doing real innovation. (LLM architectures and such.)
Everyone else is just gaming engagement metrics and benchmarks.
Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#476Earlier quoted context omitted.
Poor babies. Again, I don’t care about them.
it's not about the companies, what a myopic viewpoint every delay to AGI results in deaths that AGI could have prevented. we are talking millions of deaths for, say, just a year's delay.
- you are assuming that an AGI will prevent more deaths than it would cause
- you are assuming that AGI is just around the corner and that scaling up language models is the path to get there
- you can make this argument about basically anything (nuclear power, tuberculosis medication, free healthcare). I’d say the burden of proof is on you to back up your extraordinary claim with extraordinary evidence.
Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#477Earlier quoted context omitted.
Poor babies. Again, I don’t care about them.
it's not about the companies, what a myopic viewpoint every delay to AGI results in deaths that AGI could have prevented. we are talking millions of deaths for, say, just a year's delay.
> every delay to AGI results in deaths that AGI could have prevented
Uhm, that's not what Hollywood told me. I trust the screenwriters of "Terminator" more than I trust your anonymous forum comment.
Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#478The 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…
> The frustration regex is funny but honestly the right call.
I love that it only supports English. AI bubble in a nutshell.
Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#479Earlier quoted context omitted.
Poor babies. Again, I don’t care about them.
it's not about the companies, what a myopic viewpoint every delay to AGI results in deaths that AGI could have prevented. we are talking millions of deaths for, say, just a year's delay.
> every delay to AGI results in deaths that AGI could have prevented
Sure, that's what AGI would be used for /s
In other news, we are not even close to AGI and even with the current experimental technology, frontier AI model companies are already fighting to help departments of war, which actually results in the most deaths. What makes you think AGI would be used for not leading to the same millions of deaths?
Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#480Earlier quoted context omitted.
You're confused, AI can't itself hold copyright, but the human who triggered the AI to write the code holds the copyright instead.
No the human cannot hold the copyright also. They can own the property rights to the code and protect it. It's not like the rule is "AI cannot copyright stuff but humans can" but rather code is rarely copyrighted and in its case, ownership is much more important. If your code was generated by you and you store it in your system and have property rights over it, you can enforce legal actions even without holding a cop…
“Loop structure for operations in memory”
https://patents.google.com/patent/US9583163B2/en
> How do you patent a for-loop for example