Boris Cherny: How We Built Claude Code

| Business & Entrepreneurship | February 17, 2026 | 204 Thousand views | 50:11

TL;DR

Boris Cherny reveals how Claude Code emerged accidentally from a terminal prototype built to test Anthropic's API, emphasizing the philosophy of building for AI capabilities six months in the future rather than today's limitations, and evolving the product through observing latent user demand rather than rigid roadmaps.

🚀 Building for Tomorrow's Models 3 insights

Target frontier capabilities, not current limitations

Cherny advises founders to build for where models will be in six months, as capabilities improve rapidly. Claude Code was architected assuming models would eventually excel at coding tasks they initially performed poorly.

Aggressive rewriting over code preservation

The entire codebase has been rewritten multiple times over six months as capabilities evolved, with no original code remaining. This reflects a willingness to discard work as model capabilities make old scaffolding obsolete.

Plan mode obsolescence timeline

Cherny predicts explicit planning modes may become unnecessary within a month as models become capable of autonomous reasoning without structured prompting or explicit instructions.

🎯 Accidental Origins & Latent Demand 3 insights

Terminal as constraint, not strategy

The CLI form factor emerged accidentally because it required no UI development, not from strategic planning. This constraint became a strength, making the tool accessible without requiring knowledge of Vim, Tmux, or complex IDE configurations.

Users reveal needs through behavior

The team discovered latent demand by observing engineers creating markdown instruction files for the model, which evolved into the formal Claude MD feature rather than being designed top-down.

Organic viral adoption

Internal usage charts showed vertical growth without mandates—engineers shared the tool virally after Boris posted about it, with colleagues adopting it immediately despite prototype status.

🛠️ Minimalist Design Philosophy 3 insights

Shared context over personal prompts

Cherny maintains a minimal two-line personal Claude MD, storing all instructions in a shared codebase file that the team updates multiple times weekly, treating AI mistakes as opportunities to improve collective documentation.

Verbosity as debuggability feature

Attempts to summarize bash output faced user revolt because developers need transparency to catch when models go wrong, leading to configurable verbosity modes rather than forced brevity.

Delete and restart approach

When Claude MD grows too large, Cherny recommends deleting it entirely and starting fresh, adding back only what the new model strictly requires, as older scaffolding becomes unnecessary with capability advances.

Bottom Line

Build the simplest possible interface that solves today's problem while architecting for rapid obsolescence, because AI capabilities improve fast enough to invalidate complex scaffolding within months.

More from Y Combinator

View all
Why Domain Experts Are Winning Right Now
42:43
Y Combinator Y Combinator

Why Domain Experts Are Winning Right Now

Bryant Chou, co-founder of Webflow, demonstrates how his new startup Ploy enables domain experts to autonomously execute world-class marketing and web design, arguing that deep industry experience is becoming the ultimate competitive advantage for leveraging AI effectively.

5 days ago · 9 points
5 Papers That Show Where AI Research Is Heading Right Now
1:16:55
Y Combinator Y Combinator

5 Papers That Show Where AI Research Is Heading Right Now

Researchers argue that achieving AGI requires moving beyond human-generated training data toward AlphaZero-style self-play methods, while highlighting critical unsolved challenges in learning efficiency per sample and per watt. A detailed presentation demonstrates that protein biology models now follow the same predictable scaling laws as language models, with the ESMC model showing continuous improvement when trained on 2.8 billion sequences compared to previous plateaus at 50 million.

12 days ago · 6 points
How Meesho Became India’s Biggest Shopping App
30:21
Y Combinator Y Combinator

How Meesho Became India’s Biggest Shopping App

Meesho founder Vidit Aatrey details how the company pivoted from a failed local shopping app to India's largest e-commerce platform with 250 million users, achieving product-market fit by empowering WhatsApp-based resellers and focusing on value-conscious consumers in 'mass India.'

13 days ago · 9 points