Claude is Now Building Itself
Claude is Now Building Itself
Wednesday, April 29, 2026
Tech-Reader AI Digest Special Edition
#AI #TechNews #Digest
We Build Claude With Claude — And That Changes Everything
Something remarkable is happening inside the walls of one of the world's most advanced AI laboratories — and it isn't getting the attention it deserves.
Boris Cherny, the head of Anthropic's Claude Code, has not written a single line of code by hand in more than two months. Not a function. Not a variable assignment. Not even a small edit. Every pull request — 22 one day, 27 the next — written entirely by Claude.
Across Anthropic as a whole, Cherny says "pretty much 100%" of code is now AI-generated. Anthropic's official position, stated plainly: "We build Claude with Claude."
Let that land for a moment.
What this actually means.
This is not a productivity story. It is not a "developers are using AI assistants" story. It is something categorically different: the model is participating in its own construction.
Claude Code — Anthropic's agentic coding tool — writes approximately 90% of its own codebase. The engineers who build Claude are no longer writing the instructions that make Claude. Claude is. The loop is closing.
Cherny described what this feels like from the inside: "I have never had this much joy day to day in my work, as I do right now, because essentially all the tedious work, Claude does it, and I get to be creative. I get to think about what I want to build next."
That is not a quote about productivity. That is a quote about a fundamental shift in what a software engineer actually does.
The numbers behind the claim.
Cherny's personal figure — 100% for two-plus months — is the most striking data point, but it is not the only one. Anthropic company-wide sits at 70–90% by the company's own spokesperson account. Claude Code itself sits at approximately 90% self-generated. Cherny's team built Cowork — Anthropic's new desktop automation agent — in roughly a week and a half, using Claude Code to build it.
For context: Dario Amodei said at Davos earlier this year that some Anthropic engineers have stopped writing code entirely and now focus exclusively on editing and direction. He predicted AI would handle most or all of software engineering end-to-end within six to twelve months of that statement.
That window is now.
What it means for the rest of the industry.
Cherny was direct: "I think most of the industry will see similar stats in the coming months — it will take more time for some vs others. We will then start seeing similar stats for non-coding computer work also."
That last sentence deserves its own paragraph. Non-coding computer work. The same feedback loop that consumed software engineering is coming for the broader category of knowledge work performed on computers.
Cherny's team already reflects the new hiring reality. Anthropic now hires generalists over specialists because traditional programming skills matter less when Claude handles implementation. "The model can fill in the details," he said.
Why this is the real story of 2026.
The enterprise AI conversation this year has focused on deployment numbers, valuation rounds, and productivity statistics. Those matter. But the deeper story — the one with the longest tail — is this one.
The people building the most powerful AI models on the planet have handed implementation of those models to the models themselves. That is not a feature announcement. It is a civilizational data point.
We are not watching AI assist human engineers. We are watching the boundary between human authorship and machine authorship dissolve — inside the lab where the machine is made.
Aaron's take — Boris didn't bury this. He posted it on X, matter-of-factly, in response to Andrej Karpathy. Twenty-two pull requests. Twenty-seven pull requests. One hundred percent Claude. The casualness of the disclosure is almost more striking than the disclosure itself. This is already the new normal inside Anthropic. The question is how long before it's the new normal everywhere else — and what that means for everyone who builds things for a living.
(Source: Boris Cherny on X)
Aaron Rose is a software engineer and technology writer at tech-reader.blog.
Catch up on the latest explainer videos, podcasts, and industry discussions below.
.jpeg)

Comments
Post a Comment