Claude leads 26% of AI R&D at Anthropic. Who checks it?

Anthropic says Claude led 26% of its internal AI research and development work in an August 2026 snapshot, with humans supervising. Its 17 September report finds none of the measured work fully autonomous. My takeaway is that directing research and checking its results need to be measured separately. [1]

What does Claude leading 26% of research mean?

It means Claude takes the lead on work while a person supervises, according to Anthropic’s classification. That is different from doing research without a human. The distinction matters because a system can decide how to carry out a task while still depending on somebody else to judge whether the result is useful. [1]

The 17 September Reddit discussion in r/singularity picked up the 26% figure. I think it is a useful reason to read the underlying report, especially because the word “leading” invites a much broader interpretation than the measurement requires. A developer who hears it may imagine an AI choosing a research programme, running the experiments and deciding what to ship. Those are separate responsibilities. [2]

Here is how I would separate them when evaluating an agent in my own work. This is a review framework, not Anthropic’s official scoring table.

Delegating the middle row does not settle the other two. That is also the distinction behind my earlier discussion of Opus 5’s coding and supervision problems: producing a substantial result and making that result easy to trust are different properties.

How was the percentage measured?

Anthropic describes an internal estimate built from work records and model-assisted classification. Its weighting uses person-time as a proxy, distributing a person’s weekly weight across their tasks. The result is a way to track changes in how work is done, rather than a direct measurement of hours saved. [1]

That denominator changes how I read the headline. “AI leads a share of the work” cannot simply become “we need that share fewer people.” To make the second claim, I would want to know what the people do after delegation, how much time they spend reviewing, and whether the accepted output has changed in quality or volume.

Consider a hypothetical engineer who delegates an experiment, then spends the afternoon checking whether its test setup was valid. The agent may have led execution while the engineer still spent substantial time on the project. Alternatively, the same engineer might review several useful experiments in the time previously needed for one. A task classification alone cannot tell those situations apart.

I would use the report to identify questions for a more detailed evaluation, much as I use AI benchmark comparisons to decide what deserves testing. The useful follow-up is to connect delegation with accepted outcomes and review effort. Otherwise, a team can measure more AI activity without learning whether its work improved.

Does this mean AI is improving itself autonomously?

Anthropic’s separate essay, When AI builds itself, says recursive self-improvement has not yet been reached and is not inevitable. It also identifies choosing research goals and judging results as areas where human expertise remains important. That makes this a report about the organisation of research, not evidence that the entire development cycle runs itself. [3]

Recursive self-improvement would require more than an AI contributing code to the next model. The interesting claim is that improvements enable the system to carry out further improvements with less dependence on people. Evidence for one useful contribution does not establish that continuing process. I examine the same distinction in Z.ai’s account of using GLM to optimise inference software.

My read is that the immediate pressure falls on verification. If generating a proposed experiment becomes easier, somebody still needs to decide whether the experiment answers the question. A polished explanation of a bad test can make that job harder by giving the reviewer more plausible material to check.

For that reason, I would keep the mechanism that produces an answer separate from the evidence used to accept it. In software work, that might mean checking behaviour against requirements and tests that were not rewritten to accommodate the patch. In research, it means asking what result would challenge the proposed explanation. These are evaluation choices, not additional findings from Anthropic’s report.

What would I change in a coding workflow?

I would make the review requirement explicit before delegating a larger task. The agent needs a clear output, but the reviewer also needs a way to establish that the output is correct. That is a more useful response to this report than simply increasing the number of agents.

For an investigation, I would ask for the evidence behind the conclusion and any unresolved contradiction. For a code change, I would ask which behaviour changed and how it was checked. I would then assess whether the review takes less effort than doing the work directly, including the time spent correcting an initially convincing mistake.

The same question belongs in the design of applications built around the OpenAI Agents API. An application can delegate execution while keeping acceptance with the person responsible for the result. Deciding where that acceptance happens is part of the product design.

For the next model release, I would pay attention to what a reviewer can verify after a long run. A model that completes more work is useful; knowing which parts are safe to rely on determines how much of that work I can actually accept.