Anthropic CEO Discusses Share of AI-Generated Code

According to Tech Trenches, Dario Amodei, CEO of Anthropic, said in March 2025, "We're 3 to 6 months from a world where AI is writing 90% of the code." Tech Trenches documents subsequent public remarks and internal-facing posts it links to: a December 27, 2025 X post by Boris Cherny stating "In the last thirty days, 100% of my contributions to Claude Code were written by Claude Code," and a March 2025 Benioff interview snippet Tech Trenches reports where Amodei said "That is absolutely true now," while also adding qualifiers such as "not uniformly." Tech Trenches additionally cites a February 2026 product comment by Mike Krieger reported as saying for many products it is "effectively 100%."

Redwood Research's blog post explicitly questions the definitional basis for the percentages, noting the difference between metrics such as lines merged, commits authored, characters typed, or "any code that was at all useful." Redwood Research argues that some teams can reach very high AI-written fractions for merged lines, while company-wide averages are likely lower; its public writeup estimates a figure nearer 50% for merged lines across Anthropic but explains this depends strongly on inclusion rules. Industry practitioners will recognize that these measurement choices materially change any headline percentage.

Public reporting and internal claims about Claude Code mirror broader sector discussions about how to measure AI contribution to software engineering. Observers and researchers repeatedly warn that percentages without a clear metric are misleading. Tech Trenches highlights concrete risks visible in the leaked codebase it reviewed: a large TypeScript codebase with a single 3,167-line function, regex-based sentiment heuristics, and a documented bug consuming 250,000 API calls daily. Those artifacts illustrate operational and maintenance questions that follow heavy automated code generation.

For practitioners: track how organizations define and audit AI-written code (lines merged vs. engineered, test coverage, security reviews). For researchers: look for reproducible measurements or public engineering postmortems that state counting rules. For risk teams: monitor leaked/internal code reviews and bug disclosures that may reveal failure modes unique to high-volume generated code.

The factual claims above are drawn from Tech Trenches reporting of public remarks and posts and from Redwood Research's written analysis; Redwood Research provides the skeptical measurement framing and alternative estimates.