The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
351–360 of 636 posts
Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#352Earlier quoted context omitted.
If those tools are writing the code then in general I do expect that to be included in the PR! Through my whole career I've seen PRs where people noted that code that was generated (people have been generating code since long before LLMs). It's useful context unless you've gone over the generated code and understand it and it is the same quality as if you wrote it yourself (which in my experience is the case where it…
> It's useful context unless you've gone over the generated code and understand it and it is the same quality as if you wrote it yourself If this is not the case you should not be sending it to public repos for review at all. It is rude and insulting to expect the people maintaining these repos to review code that nobody bothered to read.
The difference here is that the generator is a non-deterministic LLM and you can't reason about its output the same way.
Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#353Earlier quoted context omitted.
well you know 100% know what dependabot does
Leaves you open to vulnerabilities in overnight builds of NPM packages that increasingly happen due to LLM slop?
Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#354Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#355Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#356Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#357Earlier quoted context omitted.
I didn't even know there was a "three em dash". Bravo.
Huh. It's displayed taking up three cells in my terminal, but laid out as if its width were one cell. Irritating. I wonder if there are any other grapheme clusters that don't properly fit in two cells?
Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#358There are now several comments that (incorrectly?) interpret the undercover mode as only hiding internal information. Excerpts from the actual prompt[0]: NEVER include in commit messages or PR descriptions: - The phrase "Claude Code" or any mention that you are an AI - Co-Authored-By lines or any other attribution BAD (never write these): - 1-shotted by claude-opus-4-6 - Generated with Claude Code - Co-Authored-By: C…
I cringe every time I see Claude trying to co-author a commit. The git history is expected to track accountability and ownership, not your Bill of Tools. Should I also co-author my PRs with my linter, intellisense and IDE?
Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#359I’m more curious how this impacts trust than anything else. In the span of basically a week, they accidentally leaked Mythos, and then now the entire codebase of CC. All while many people are complaining about their usage limits being consumed quickly. Individually, each issue is manageable (Because its exciting looking through leaked code). But together, it starts to feel like a pattern. At some point, I think the q…
Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#360Earlier quoted context omitted.
> frying a veggie burger in bacon grease hmm gotta try that
I love black bean burgers (bongo burger near Berkeley is my classic), sounds like an interesting twist