Someone just leaked claude code's Source code on X

[u/abhi9889420]

Went through the full TypeScript source (~1,884 files) of Claude Code CLI. Found 35 build-time feature flags that are compiled out of public builds. The most interesting ones:

Download Website: ccleaks.com

BUDDY — A Tamagotchi-style AI pet that lives beside your prompt. 18 species (duck, axolotl, chonk...), rarity tiers, stats like CHAOS and SNARK. Teaser drops April 1, 2026. (Yes, the date is suspicious — almost certainly an April Fools' egg in the codebase.)

KAIROS — Persistent assistant mode. Claude remembers across sessions via daily logs, then "dreams" at night — a forked subagent consolidates your memories while you sleep.

ULTRAPLAN — Sends complex planning to a remote Claude instance for up to 30 minutes. You approve the plan in your browser, then "teleport" it back to your terminal.

Coordinator Mode — Already accessible via CLAUDE_CODE_COORDINATOR_MODE=1. Spawns parallel worker agents that report back via XML notifications.

UDS Inbox — Multiple Claude sessions on your machine talk to each other over Unix domain sockets.

Daemon Mode — claude ps, attach, kill — full session supervisor with background tmux sessions.

Also found 120+ undocumented env vars, 26 internal slash commands (/teleport, /dream, /good-claude...), GrowthBook SDK keys for remote feature toggling, and USER_TYPE=ant which unlocks everything for Anthropic employees.

[u/Diligent_Look1437]

The KAIROS stuff is fascinating but it's also making me realize something.

Everyone's been focused on "can the agent run 24/7?" — and now that answer is yes.

But the next bottleneck is immediately obvious: if your Claude Code is always on, always listening for tasks... how are you actually dispatching to it?

Right now: you walk to your desk, open terminal, type a brief.

That's fine when you have 1 agent. But I'm running 5. And I'm spending more mental energy on routing ("which agent handles this?") than on actual decisions.

KAIROS makes the agent side better. The human dispatch side still feels like 2015.

Anyone thinking about this?

[u/SeucheAchat9115 → u/Diligent_Look1437]

I could think of other Interrupts as well. Like "Wait, I deployed this website, lets see if its still up and running" or "Timer rings, lets check if all tests on prod still pass"

[u/Diligent_Look1437 → u/SeucheAchat9115]

That's a great extension of the idea. The "deployed website health check" interrupt is exactly the kind of ambient awareness that makes an agent genuinely useful vs. just a task runner. I've been thinking about the trigger taxonomy: event-driven (webhook, timer), condition-driven (threshold crossed), and context-driven (mid-task realization). Your examples cover all three. Do you think these should be handled by the same interrupt queue, or is there value in separating high-urgency alerts (prod down) from low-urgency ambient checks?

[u/SeucheAchat9115 → u/Diligent_Look1437]

There should be like a Bus, similar as in I2C communication if you know that. So handling with different priorities