Claude source code leak and the unreleased features hiding in the client

BUDDY appears to be a persistent companion system that places a small pet-like character beside the input box and lets it react in its own speech bubble. The client defines 18 species, rarity tiers, a 1% shiny roll, and five personality stats, with deterministic traits tied to account identity and a stored "soul" made up of name, personality, and hatch time.

KAIROS points to an assistant mode designed for ongoing, cross-session work. Instead of constantly rewriting a live memory index, it appends timestamped notes to daily local log files and relies on a separate dream-style consolidation flow to distill them into structured memory files, while long-running shell work auto-backgrounds to keep the assistant responsive.

ULTRAPLAN sends open-ended planning work to a remote Claude Code session, polls for progress every three seconds, and allows up to thirty minutes for the planning run. Users can approve execution in the browser or teleport the approved plan back to the local terminal and continue from there.

Coordinator mode turns the main Claude instance into an orchestrator that launches workers, receives structured task notifications, and synthesizes results back to the user. Under the hood, workers communicate through mailbox-style messaging, optional shared scratchpad access, and a coordination loop that feels much closer to a small agent team than a single-threaded assistant.

Auto-Dream is a forked background subagent that consolidates what matters after enough time and sessions have passed. Its workflow is explicit in the client: orient, gather recent signal, consolidate, and prune or re-index memory files, with default thresholds set to at least 24 hours and five sessions.

Bridge, surfaced as Remote Control, connects a local Claude Code session to claude.ai/code and Claude Desktop so work can continue across devices. The transport layer already supports multiple protocol paths, combining streamed inbound events with HTTP-based outbound control for reconnectable remote access.

The CLI already exposes daemon and daemon-worker entrypoints, and session metadata distinguishes interactive, background, daemon, and daemon-worker modes. That strongly suggests a long-running supervisor architecture for persistent sessions, even though the full implementation is not fully visible in this source snapshot.

UDS Inbox points to a Unix domain socket messaging layer that lets local tools and sessions inject messages into Claude Code. The client includes socket startup logic, explicit socket-path options, and passive versus replay-aware behavior for headless and structured-output workflows.