Source: raw/Claude_Code_Just_Leaked_Its_Entire_Source_Code_Here_s_What_s_Inside.md Creator: Robo Nuggets (Jay) URL: https://www.youtube.com/watch?v=wGtOMkoi35s Duration: 6:59 Platform: YouTube Published: 2026-04-01

At the end of March 2026 a Claude Code release shipped with a source map that exposed its source code, and Jay of Robo Nuggets walked through what people found in it. This is a historical record, seven months old at ingest. Its value now is the scorecard: which leaked features shipped, which shipped and were later removed, and which never appeared in this wiki’s release coverage. Everything in the leak section is Jay’s reading of a mirrored codebase, not Anthropic’s documentation.

Key Takeaways

  • What leaked, per Jay. A 60 MB source map in “the latest version of Claude Code”, about 2,000 files and over 500,000 lines. A security researcher found it first and the code was mirrored to GitHub within hours. The model weights were not in it: “Claude Code is just a harness.”
  • Most of the leaked roadmap shipped in some form within weeks. Ultraplan reached a research preview in Week 15 (and was removed in August); /buddy shipped as an April 1 gag in Week 14; the “YOLO classifier” is what Jay maps to auto mode, which had already shipped a week earlier; Auto Dream became Claude Code’s memory-consolidation pass. ^[inferred — the mapping to later releases is this article’s, from the wiki’s digests]
  • Two items never surfaced in this wiki’s release coverage: the always-on “KAIROS” daemon (caption “Kyros”) and “undercover mode.” Treat both as unconfirmed.
  • Jay’s thesis: Claude Code was being built into “an operating system for agents,” copying what OpenClaw had popularised (daemons, phone notifications, memory consolidation). That direction did play out through channels, Routines and the Monitor tool.
  • The practical lesson is about your own packages, not Anthropic’s. A source map published with a build is enough to expose a codebase. Check what your own build artifacts include before you publish them.

What Jay found in the leak

Leaked itemWhat Jay says it doesWhat later happened (wiki record)
KAIROS (“Kyros” in captions)Always-on proactive background agent running as a daemon. A 15-second budget per action; exclusive tools to send files, notify your phone and subscribe to pull requestsNot documented in this wiki as a shipped feature. The nearest shipped pieces are Channels (phone messaging), the Monitor tool (background watchers) and Routines (cloud scheduling) ^[inferred]
BuddyA Tamagotchi-style ASCII pet in the terminal: 18 species (Jay names Chonk, caption “Chomk”, Capybara, Dragon, Ghost) with rarity tiers up to legendaryShipped as /buddy, an April 1 gag, in Week 14
UltraplanSends a hard problem to a cloud machine running Anthropic’s strongest model and gives it up to 30 minutes to thinkShipped as a research preview in Week 15; removed in v2.1.222 on 2026-08-04 (see Ultraplan)
Model codenamesCapybara (Jay guesses Opus 5, and “the mythos model”), Fennec (caption “Fenec”, likely Sonnet), Numbat (likely Haiku)Jay’s guesses ^[ambiguous]. The wiki’s model record is in Claude Fable 5 + Mythos 5
Undercover modeScrubs anything in commit messages that would reveal an AI wrote the change. Jay’s theory: so enterprise customers can “use AI quietly”Not documented in this wiki. Claude Code’s commit attribution is configurable in settings (see CLI reference, attribution.*) ^[inferred]
Auto DreamA background subagent that consolidates and prunes Claude Code’s memories when idle. Jay says it was already rolling out unofficiallyDocumented as the consolidation pass in Auto Memory
YOLO classifierDecides whether to ask the user or proceed automaticallyJay equates it with auto mode, which shipped for Team users on about March 24 (Week 13)
Frustration detectionSentiment analysis on user messages (specific words, repeated questions, short angry replies) to improve the productNot documented in this wiki

Try It

  1. Use the scorecard, not the leak. For any feature named above, go to the linked wiki article for how it actually shipped. Ultraplan in particular is gone; use the surviving delegation patterns listed in Ultraplan.
  2. Audit your own published packages. Before publishing an npm package or a web build, list the files it will ship (for npm, npm pack --dry-run) and confirm no .map files or unminified sources are included unless you mean to publish them.
  3. Read leak coverage as a forecast with a short shelf life. Jay’s roadmap reading was mostly right on direction and partly wrong on persistence (Ultraplan shipped, then was removed).

Open Questions

  • Which version leaked, and how did Anthropic respond? The source gives neither the version number nor Anthropic’s statement. Not checked against a primary source here.
  • Did KAIROS ever ship under another name? No wiki release digest names it.
  • Undercover mode and frustration detection rest only on Jay’s reading of the mirrored code.
  • The codename mapping (Capybara, Fennec, Numbat) is the creator’s speculation.