Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

alex000kim.com

Post reply on HN
Print view View original

41–50 of 636 posts

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

#41

Post by otterley »

mzajc wrote: post #37

There 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 would have expected people (maybe a small minority, but that includes myself) to have already instructed Claude to do this. It’s a trivial instruction to add to your CLAUDE.md file.

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

#42

Post by saadn92 »

The feature flag names alone are more revealing than the code. KAIROS, the anti-distillation flags, model codenames those are product strategy decisions that competitors can now plan around. You can refactor code in a week. You can't un-leak a roadmap.

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

#43

Post by andoando »

mzajc wrote: post #37

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

Ive seen it say coauthored by claude code on my prs...and I agree I dont want it to do that

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

#44

Post by simianwords »

__blockcipher__ wrote: post #33
simianwords wrote: post #8

Guys I’m somewhat suspicious of all the leaks from Anthropic and think it may be intentional. Remember the leaked blog about Mythos?

I'm normally suspicious but honestly they've been so massively supply-constrained that I don't think it really benefits them much. They're not worried about getting enough demand for the new models; they're worrying about keeping up with it. Granted, there's a small counterargument for mythos which is that it's probably going to be API-only not subscription

Why would Claude code mention Mythos then

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

#45

Post by andoando »

peacebeard wrote: post #14

The name "Undercover mode" and the line `The phrase "Claude Code" or any mention that you are an AI` sound spooky, but after reading the source my first knee-jerk reaction wouldn't be "this is for pretending to be human" given that the file is largely about hiding Anthropic internal information such as code names. I encourage looking at the source itself in order to draw your conclusions, it's very short: https://git…

I think the motivation is to let developers use it for work without making it obvious theyre using AI

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

#46

Post by petcat »

mzajc wrote: post #37

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

It's less about pretending to be a human and more about not inviting scrutiny and ridicule toward Claude if the code quality is bad. They want the real human to appear to be responsible for accepting Claud's poor output.

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

#48

Post by peacebeard »

stordoff wrote: post #32
peacebeard wrote: post #24

Earlier quoted context omitted.

~That line isn't in the file I linked, care to share the context? Seems pretty innocuous on its own.~ [edit] Never mind, find in page fail on my end.

It's in line 56-57.

Thanks! I must have had a typo when I searched the page.

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

#49

Post by hombre_fatal »

mzajc wrote: post #37

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

You can already turn off "Co-Authored-By" via Claude Code config. This is what their docs show:

~/.claude/settings.json

    {
      "attribution": {
        "commit": "",
        "pr": ""
    },
The rest of the prompt is pretty clear that it's talking about internal use.

Claude Code users aren't the ones worried about leaking "internal model codenames" nor "unreleased model opus-4-8" nor Slack channel names. Though, nobody would want that crap in their generated docs/code anyways.

Seems like a nothingburger, and everyone seems to be fantasizing about "undercover mode" rather than engaging with the details.

Post reply on HN