Ok hear me out, I know the leak discourse has been mostly about the drama and the memes but I’ve been actually reading the code and trying to understand how Claude Code makes decisions internally. And then I started prompting it differently based on what I found and the results are kind of blowing my mind. The leaked source shows that Claude Code uses a multi-agent orchestration system internally. There’s a coordinator mode that spawns parallel workers,there’s a 40+ tool registry with risk classifications LOW, MEDIUM, HIGH and an ML based auto approval system. There’s something called ULTRAPLAN that runs 30min remote planning sessions. And threading through a lot of this is Mythos, which from context seems to be the system that handles how Claude builds and maintains its understanding of what it’s working on. So I thought what if I prompt Claude Code in a way that aligns with how it’s actually structured internally instead of just throwing tasks at it? Here’s what I changed Instead of saying “refactor this authentication module” I now break my prompts into the same pattern the coordinator mode seems to use. I give it an explicit planning phase first “Before writing any code, analyze the current auth module and produce a plan covering: files affected, dependencies, risk level of each change, and execution order.” Then I let it plan. Then I say “execute the plan.” The difference is staggering. Before, Claude Code would dive straight in, make changes, break something three files away, then spend 20 minutes fixing what it broke. Now it maps the whole thing out first, flags the high-risk changes, and executes in an order that doesn’t cascade failures. I also started mimicking the risk classification system from the source. I explicitly tag parts of my request: “this is a LOW risk formatting change” vs “this is a HIGH risk database migration.” Claude Code’s behavior shifts noticeably. On the HIGH risk tags it becomes more conservative, asks more clarifying questions, and generates more defensive code with better error handling. It was probably always capable of this but the explicit risk framing seems to activate a different mode. The Mythos connection is what interests me most though. From the source it looks like Mythos might be how Claude maintains a coherent understanding across long sessions like an internal narrative of what it’s building and why. So I started giving Claude Code explicit narrative context at the start of sessions. Giving it a narrative instead of just a file tree changed how it prioritizes and it became more careful around auth code and more confident making changes to the API layer. Almost like it internalized the project’s history and is making judgment calls based on institutional knowledge rather than just file analysis. i also tried generating a short demo video of the before/after workflow using Kling and magic hour to make a visual walkthrough for my team. The irony is that none of this required the leak,Claude code was always capable of working this way. But seeing the internal architecture made me realize I was prompting a multi-agent planning system like it was a simple chatbot.We’ve been driving a race car in first gear. Curious if anyone else has been adapting their prompting based on what the source revealed. Specifically around the Mythos related patterns and the coordinator mode submitted by /u/Tough_Commercial_103
Originally posted by u/Tough_Commercial_103 on r/ClaudeCode