Anthropic's New AI-R&D Metrics Make Frontier Development More Observable
Anthropic has published a prototype way to measure how much AI performs AI R&D, how agent actions are overseen, and how compute is allocated. The useful signal is the measurement framework, not one headline percentage.
Anthropic's September 17, 2026 release is important because it turns part of the pace-of-AI-development debate into a measurement problem. The company published a prototype index for how much of its AI R&D is performed by Claude, alongside metrics for agent oversight and compute allocation. The strongest signal is not the headline number; it is the attempt to define measurements that could be repeated and, eventually, checked outside Anthropic. Anthropic's primary release
What Anthropic is measuring
Anthropic proposes three observation surfaces.
First is AI-led AI R&D: how much of the work involved in building future models is itself performed by AI. Anthropic created an R&D Automation Index by cataloguing model-R&D tasks, assigning each an automation level, and aggregating those ratings.
Second is agent oversight: whether actions taken by research and engineering agents pass through monitoring, how quickly review happens, and how often monitoring blocks or escalates activity.
Third is compute allocation: where the resources used to develop models are actually being spent.
These are different measurements with different denominators. Combining them into one generic "AI progress" score would lose information.
The 26% figure needs careful handling
Anthropic says that, as of August 2026, Claude "leads" 26% of the company's measured AI R&D work. On its scale, "leads" means the model can complete most of a task end-to-end from a high-level prompt while a human supervises. Anthropic also says that more than 90% of the measured work sits at or above the "AI collaborates" level, while no measured subset is fully autonomous. Anthropic and Engadget independently describe the release.
Those numbers are useful as Anthropic's own internal measurement, not as a universal estimate of frontier-lab automation.
The company sampled staff work across several weeks, constructed a task hierarchy, and used Claude-based researchers and judges to classify tasks. It also acknowledges a direct methodological problem: a model is being used to assess how much another model is doing. Anthropic says cross-lab comparison would require a common methodology and some form of independent verification.
That limitation is central, not peripheral.
The measurement design is the more durable signal
The most interesting part of the release is the attempt to freeze a consistent basket of work so that later measurements can be compared with earlier ones.
Anthropic describes a hierarchy containing hundreds of task categories. It samples work, classifies activities, assigns automation levels, and uses person-time as a weight for aggregation. The goal is to prevent a headline percentage from changing simply because the definition of the workload changed.
That is exactly the problem good observatories face.
A metric is only comparable over time when its measurement system is stable enough to make the comparison meaningful. Changing the task taxonomy, the rating scale, the sampling process, or the weighting can create an artificial trend.
The Observatory's own rule is the same: measurement first, interpretation second.
Agent oversight is a second signal worth watching
Anthropic also reports approximately 30,000 research and engineering agents on its most-used internal platform as of August 2026. It says every action passed through an online monitor before execution, while actions were also ingested into an offline monitoring system.
In August, Anthropic says it analyzed more than one billion online-monitoring decisions. About 0.002% were blocked, or roughly one in 47,000. The offline system flagged roughly one to two transcripts per thousand for further review, with higher-priority cases escalated to humans.
Those figures should not be converted into a simple "failure rate."
A block can mean a false positive, a deliberately adversarial test, or a genuinely dangerous action. A monitor's escalation rate also depends on the threshold chosen by the monitoring system. The useful questions are therefore about coverage, latency, false-positive handling, and what happened after escalation, not just the raw rate.
Anthropic itself describes those three dimensions—coverage, review latency, and escalation rate—as the core measurements.
Why this is becoming an observability problem
As agents take longer actions and interact with more tools, "what the model can do" becomes only part of the question.
A public capability benchmark might tell us that a model can solve a research task. It does not tell us:
- how much supervision was required,
- how often a human had to intervene,
- how many attempts were blocked,
- how expensive the run was,
- how much of the surrounding engineering work was automated,
- or whether the same level of automation persists over time.
Anthropic's proposal starts connecting those dimensions.
Independent research from Epoch AI has been exploring a similar problem from outside a model vendor: how to define task-level measures for AI automation in R&D. METR provides another independent reference point for evaluating risks from increasingly capable models and agents.
The approaches are not standardized, but they are beginning to converge on a common need: make the work process observable, not just the final model capability.
What could make these metrics useful across labs
For the measurements to become genuinely comparative, at least four things are needed.
A common task vocabulary
Two labs cannot compare "70% automated" if they mean different work. A shared taxonomy, or a clear translation layer between taxonomies, would be necessary.
A stable rating scale
"Collaborates," "leads," and "autonomous" are intuitive labels, but the operational definitions need to stay fixed and auditable.
Independent evaluation
A lab measuring its own systems has incentives and blind spots. Anthropic explicitly proposes external third-party evaluators with access to internal processes, systems, and data.
Time-series publication
A single snapshot is descriptive. Repeated measurements are what let researchers examine acceleration, plateaus, or changes after new safeguards are introduced.
Those requirements are harder than publishing a single percentage—but they are what would turn a press release into a research instrument.
What the evidence does and does not prove
Observed: Anthropic published three new measurement families on September 17, 2026, including a prototype R&D Automation Index and agent-oversight measurements. Primary source
Reported by Anthropic: Claude "leads" 26% of measured AI R&D work as of August 2026, and the company reports about 30,000 research and engineering agents on its most-used internal platform.
Independent context: Engadget covered the measurements, while Epoch AI and METR provide independent measurement and risk frameworks for related questions. Their methods are not interchangeable.
Unknown: There is no industry-wide standard yet. Anthropic's methodology depends on company-internal data and model-assisted evaluation, so cross-lab comparisons remain an open research problem.
The defensible conclusion is therefore narrower than "AI is rapidly replacing AI researchers":
Anthropic has made the pace of AI-driven AI development more measurable by publishing a repeatable internal framework for R&D automation and agent oversight; the framework's comparability across labs is not established yet.
Why this belongs in a Digital Observatory
The Observatory already treats public numbers as signals rather than verdicts in Signals Are Not Truth. Anthropic's release is a useful extension of that idea because the company is exposing measurements of the production process behind AI systems, not only benchmark scores for the finished systems.
That creates a new series worth watching: whether other labs publish comparable metrics, whether the same definitions survive over time, and whether external evaluators can reproduce the results.
For continuity with the Observatory's recent work on AI behavior, compare this with OpenAI's misalignment disclosure framework. The two efforts measure different things, but both make the process around frontier AI more observable.
Sources and further reading
Evidence
Sources & further reading
Primary sources, official disclosures, and external research used to ground this report.
- Anthropic Institute — Measurements for understanding the pace of AI development inside frontier labsanthropic.com
Primary September 17, 2026 disclosure covering the R&D Automation Index, agent oversight measurements, compute allocation, and methodological limitations.
- Engadget — Anthropic says Claude 'leads' 26 percent of its AI R&D workengadget.com
Independent September 17, 2026 reporting on the newly published internal measurements.
- Epoch AI — Toward an O*NET for AI R&Depoch.ai
Independent framework work that Anthropic cites for its automation-level scale.
- METR — Risk assessmentmetr.org
Independent work on evaluating frontier-model and agent risks, useful as context for the broader measurement problem.
Keep Exploring
Related observations.
OpenAI's New Misalignment Framework Turns Rogue Model Behavior Into a Trackable Incident Class
OpenAI is moving model misalignment reporting from occasional research disclosures toward an ongoing incident process. The important signal is the reporting mechanism itself—and its limits.
Microsoft's Humanist AI Code Turns Human Control Into a Model-Level Contract
Microsoft's draft Humanist AI Code is not a technical guarantee yet, but it is unusually explicit about the intended control boundary: MAI models should accept interruption, stay within authorized scope, and fail rather than violate non-negotiable constraints.
Gemini 3.8 Live Changes the Voice-Agent Contract
The important change in Gemini 3.8 Live is not simply better voice quality. It is that conversation, reasoning, and tool execution can now overlap.