Earlier quoted context omitted.
Why would Claude code mention Mythos then
You can use Claude Code with API mode (not a sub)
fair but I'm guessing access would be limited to 20x max users or something like that. not gated by API.
The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
111–120 of 636 posts
Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#112Why didn't they open the source themselves? What's the point of all this secrecy anyway?
Because they (apparently) keep a bunch of secret features and roadmap details in said source code.
Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#113The 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…
Not leaking codenames is one thing, but explicitly removing signals that something is AI-generated feels like a pretty meaningful shift.
Doesn't seem so crazy if the point is to avoid leaking new features, models, codenames, etc.
Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#114Earlier quoted context omitted.
I think the motivation is to let developers use it for work without making it obvious theyre using AI
Which is funny given how many workplaces are requiring developers use AI, measuring their usage, and stack ranking them by how many tokens they burn. What I want is something that I can run my human-created work product through to fool my employer and its AI bean counters into thinking I used AI to make it.
I guess you could just code and have it author only the commit message
Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#115[dead]
Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#116The 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…
> my first knee-jerk reaction wouldn't be "this is for pretending to be human"... "Write commit messages as a human developer would — describe only what the code change does."
The human developer would just write what the code does, because the commit also contains an email address that identifies who wrote the commit. There's no reason to write:
> Commit f9205ab3 by dkenyser on 2026-3-31 at 16:05:
> Fixed the foobar bug by adding a baz flag - dkenyser
Because it already identified you in the commit description. The reason to add a signature to the message is that someone (or something) that isn't you is using your account, which seems like a bad idea.
Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#117Earlier quoted context omitted.
You may have a point but to drive it further, can you give an example of a thing I can do with langgraph that I can't do with Claude Code?
I'm not an supporter of blindly adopting the "langs" but langgraph is useful for deterministically reproducable orchestration. Let's say you have a particular data flow that takes an email sends it through an agent for keyword analysis the another agent for embedding then splits to two agents for sentiment analysis and translation - there is where you'd use langgraph in your service. Claude Code is a consumer tool, n…
I see what you mean. Maybe in the cases where the steps are deterministic, it might be worth moving the coordination at the code layer instead of AI layer.
What's the value add over doing it with just Python code? I mean you can represent any logic in terms of graphs and states..
Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#118Earlier quoted context omitted.
Comments are great for developers. I like having as much design in the repo directly. If not in the code, then in a markdown in the repo.
This is also a great way to ensure the documentation is up to date. It’s easier to fix the comment while you’re in the code just below it than to remember “ah yes I have to update docs/something.md because I modified src/foo/bar.ts”.
People moving docs out of code are absolutely foolish because no one is going to remember to update it consistently but the agent always updates comments in the line of sight consistently.
Agent is not going to know to look for a file to update unless instructed. Now your file is out of sync. Code comments keeping everything line of sight makes it easy and foolproof.
Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#119> Anti-distillation: injecting fake tools to poison copycats Does this mean `huggingface.co/Jackrong/Qwen3.5-27B-Claude-4.6-Opus-Reasoning-Distilled` is unusable? Had anyone seen fake tool calls working with this model?
Assuming Claude Code was used. If OpenCode or some other programmatic method was used, the "fake tool calls" won't be added
Re: The Claude Code Source Leak: fake tools, frustration regexes, undercover mode
#120Earlier quoted context omitted.
> my first knee-jerk reaction wouldn't be "this is for pretending to be human"... "Write commit messages as a human developer would — describe only what the code change does."
The human developer would just write what the code does, because the commit also contains an email address that identifies who wrote the commit. There's no reason to write: > Commit f9205ab3 by dkenyser on 2026-3-31 at 16:05: > Fixed the foobar bug by adding a baz flag - dkenyser Because it already identified you in the commit description. The reason to add a signature to the message is that someone (or something) th…
Aside from merges that combine commits from many authors onto a production branch or release tag. I would personally not leave an agent to do that sort of work.