Inside the Claude Code Source Leak That Attracted 15 Million Views
The article chronicles the March 31 2026 Claude Code source‑code leak caused by an exposed .map file in Anthropic's npm package, details the community’s rapid forking, a Korean developer’s Python rewrite using oh‑my‑codex, and provides a full technical overview of the CLI’s architecture, size, and related resources.
On March 31 2026 a Twitter user reported that the Claude Code npm package contained a .map file exposing the complete, un‑obfuscated TypeScript source, which could be downloaded as a zip from Anthropic’s R2 bucket.
A Korean developer, identified as sigridjineth, backed up the leaked version, prompting a surge of over 50 000 forks on GitHub within hours. Fearing legal action from Anthropic, the developer rewrote the code in Python using the oh‑my‑codex (OmX) workflow, employing a large language model for parallel code review and architect‑level validation.
The original leaked repository is available at https://github.com/instructkr/claude-code, while the Python rewrite resides at https://github.com/Yeachan-Heo/oh-my-codex. The leaked repo no longer contains the original source code.
Community members have produced additional resources, including a "Claude Code Design Guide" ( https://github.com/6551Team/claude-code-design-guide) and a "Claude Code Deep Dive Report" ( https://github.com/tvytlx/claude-code-deep-dive), both analyzing the design philosophy and hidden features of the tool.
The leaked codebase implements a CLI for interacting with Claude from the terminal, supporting file editing, command execution, code‑base search, and workflow coordination.
Key data: exposure date 2026‑03‑31; language TypeScript; runtime Bun; terminal UI built with React + Ink; approximately 1 900 files and over 512 000 lines of code.
src/
├── main.tsx # entry point (Commander.js CLI routing)
├── commands.ts # command registry
├── tools.ts # tool registry
├── Tool.ts # tool type definitions
├── QueryEngine.ts # LLM query engine
├── context.ts # system/user context collection
├── cost-tracker.ts # token cost tracking
│
├── commands/ # ~50 slash command implementations
├── tools/ # ~40 agent tool implementations
├── components/ # ~140 Ink UI components
├── hooks/ # React hooks
├── services/ # external service integrations
├── screens/ # full‑screen UI (Doctor, REPL, Resume)
├── types/ # TypeScript type definitions
├── utils/ # utility functions
│
├── bridge/ # IDE and remote control bridge
├── coordinator/ # multi‑agent coordinator
├── plugins/ # plugin system
├── skills/ # skill system
├── keybindings/ # key‑binding configuration
├── vim/ # Vim mode
├── voice/ # voice input
├── remote/ # remote session
├── server/ # server mode
├── memdir/ # persistent memory directory
├── tasks/ # task management
├── state/ # state management
├── migrations/ # configuration migrations
├── schemas/ # Zod configuration schemas
├── entrypoints/ # initialization logic
├── ink/ # Ink renderer wrapper
├── buddy/ # companion bot
├── native‑ts/ # native TypeScript utilities
├── outputStyles/ # output styling
├── query/ # query pipeline
└── upstreamproxy/ # proxy configurationRelated resources include the official GitHub repository ( https://github.com/instructkr/claude-code) and the OmX project ( https://github.com/Yeachan-Heo/oh-my-codex). Technical references cited are Bun, React Ink, Commander.js, Zod, the Model Context Protocol, and the Anthropic SDK.
Important reminder: This article is intended solely to disclose the incident and should not be interpreted as encouraging or supporting any illegal activity.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
AI Open-Source Efficiency Guide
With years of experience in cloud computing and DevOps, we daily recommend top open-source projects, use tools to boost coding efficiency, and apply AI to transform your programming workflow.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
