Commentary · AI Research · Our Timeline

When AI Builds Itself

Anthropic just published a sober accounting of how far AI has come toward improving its own development. The trend lines are steep — and from where we sit, they map almost exactly onto what we have watched happen inside our own shop.

Last month, Anthropic's Marina Favaro and Jack Clark published When AI builds itself, a measured look at how close AI has come to driving its own development.[1] The headline number is hard to ignore: Anthropic engineers now ship, on average, roughly eight times as much code per quarter as they did across 2021–2025. More than 80% of the company's merged production code is now written by Claude, up from single digits before February 2025. The report is careful not to declare victory — recursive self-improvement, it stresses, is “not inevitable” — but the curves it documents are steep, and they match what we have watched happen inside our own studio almost exactly.

Bar chart from Anthropic titled 'Code contributed per person, by quarter,' flat near 1x from 2021 through 2024 then rising sharply to 8x by Q2 2026, with Claude release dates marked.
Anthropic's first chart: lines of code merged per active contributor, flat for four years, then bending sharply upward through 2025 and 2026. Image courtesy of Anthropic, reused with permission.

We are not a frontier lab. We are a small studio that builds websites, APIs, and AI integrations for real businesses. And yet the shape of Anthropic's first chart — flat through 2021–2024, then bending hard upward in 2025 — is the same shape we would draw from our own commit history. Since the start of 2025, the lines of code produced at Autonomous Agent AI have risen roughly tenfold. We did not hire ten times the engineers. We did not work ten times the hours. What changed was the tooling, and specifically the arrival of coding agents that can read a repository, plan a change, edit a dozen files, run the tests, and fix what broke — all in a single sitting.

The report breaks the last five years into stages: humans writing every line; chatbots offering snippets; agents editing files; and now agents that execute, verify, and delegate. We lived that progression on a compressed timeline. In 2024 we used Claude the way you would use a very fast pair programmer — paste a function, ask for a refactor, copy it back. By the beginning of 2026, something had flipped. Today, Claude writes about 95% of the code we ship. Our engineers spend their hours where the report says human judgment still rules: deciding what to build, setting the constraints, and deciding whether the result is actually any good.

Line chart from Anthropic titled 'Claude Code session success rate,' showing four ascending lines for trivial, routine, substantial, and open-ended tasks climbing from late 2025 through mid-2026.
Success rate on internal Claude Code sessions by task difficulty. The hardest, open-ended problems climbed from the low double digits to the high seventies in under a year. Image courtesy of Anthropic, reused with permission.

That last point deserves emphasis, because the most surprising part of our own experience is not speed — it is quality. The intuition most clients bring is that more machine-written code must mean more bugs. We have found the opposite. As our share of Claude-authored code climbed past 90%, the number of defects we encounter in production went down, not up. Anthropic's own data tells the same story: code that was “somewhat worse than human-written” in late 2025 is “roughly at parity today,” and the success rate on hard, open-ended sessions has marched steadily upward across a single year of model releases. A model that runs the test suite before it hands you the diff catches a whole class of mistakes that a tired human at 6 p.m. simply misses.

The third chart is the one that should make every studio owner sit up. It asks a pointed question — when a human researcher picked a direction that turned out to be wrong, could Claude have picked better? — and the answer has crept from 22% with an early model to 64% with the most recent preview. That is no longer a tool that merely types faster than you. It is a tool that, increasingly often, has better judgment about what to do next than the person holding it.

Horizontal bar chart from Anthropic titled 'Where a researcher went wrong, could Claude have done better?' showing the share of cases where the model beat the human rising from 22% for an early model to 64% for the latest preview.
The share of cases where Claude's suggested next step beat the human researcher's, model by model. Image courtesy of Anthropic, reused with permission.

We want to be honest about the part of the report that is not a victory lap. Favaro and Clark spend their final pages on governance: the case for international coordination, for verification regimes, for keeping humans in the loop on the questions that matter most. They are explicit that a unilateral slowdown merely hands the lead to someone less cautious, and that the people who should be weighing in — policymakers, researchers, ordinary citizens — are mostly not in the room yet. We agree. The same compounding that turned our 10x into a 95% is the compounding that, taken to its end, removes the human from the loop entirely. The difference between a windfall and a hazard is whether we keep deciding what the windfall is for.

For now, our experience maps cleanly onto the optimistic-but-bounded middle scenario the report sketches: humans still set direction, AI handles execution, and output multiplies. We are living proof that a small shop can ship like one several times its size. We just think the chart should carry the same caveat Anthropic put on its own — the line is bending, and it is worth staying awake while it does.

References

  1. Favaro, M. and Clark, J. “When AI builds itself.” Anthropic. anthropic.com/institute/recursive-self-improvement

Return to Home

Want to talk through what you're reading? Book a free 30-min consult.

Book a Free 30-Min Consult

Frequently Asked Questions

Quick answers about our services, the areas we serve, and the types of projects we handle.

What services does Autonomous Agent AI offer?

We provide professional website development, custom software engineering, AI integration, workflow automation, and SEO-focused implementation. You can explore our overall approach on the home page and compare scoped delivery options on website development packages.

What areas do you serve?

We work with businesses across the Southeast, including Tennessee, Georgia, Alabama, Florida, Mississippi, and South Carolina. Visit all service areas or jump directly to Nashville, Atlanta, and Tampa location pages.

What types of work do you usually build?

We build business websites, marketing sites, resource hubs, custom app features, API-connected systems, and AI-enabled workflows. Our projects range from lean launches to large implementations, as outlined in our package tiers.

How do I choose the right website package?

Starter is best for smaller websites, Growth supports more content and integrations, and Enterprise is for complex, high-scale needs. Use the website packages page to compare scope, page counts, and included features.

Can you help if we already have a website?

Yes. We regularly improve existing sites through redesigns, SEO enhancements, performance work, and feature upgrades. If you need a custom recommendation, use our contact page and we will map next steps for your current platform.