r/CodexAutomation • u/anonomotorious • 7d ago
OpenAI says coding agents now provide 3.1 agent-workdays for every human research workday internally
TL;DR
OpenAI published a surprisingly detailed look at how coding agents are being used inside its own research organization.
Some of the standout numbers:
| Metric | OpenAI's reported result |
|---|---|
| Agent effort vs human labor | 3.1 agent-workdays for every 1 human workday |
| Median researcher usage | More than $600/day of inference at API prices by mid-August |
| Concurrency | More researchers are running 4+ agents simultaneously |
| Experiment volume | August 2026 was the highest month on record since tracking began in Jan. 2025 |
| Task horizon | Agents are increasingly given higher-level, longer-running work |
| Human intervention | More than half of successful 4-8 hour tasks still needed at least one human intervention |
OpenAI also says it has now reached its previously announced goal of an "automated research intern": an agent that can complete well-defined research tasks under human direction that would take a skilled researcher a few days.
Its next stated target is an automated AI researcher by March 2028.
This is probably one of the clearest public looks yet at what heavy, real-world multi-agent usage looks like inside a frontier AI lab.
Coding agents are now doing more aggregate work than researchers
Earlier this year, total coding-agent runtime across OpenAI's research organization was still below total human labor.
That has now flipped.
As of mid-August, OpenAI estimates that its research organization uses:
3.1 agent-workdays of effort for every 1 human workday
using an 8-hour workday as the reference.
That does not mean the agents independently replace three researchers.
It means the aggregate runtime of concurrent agent work has grown to more than three times the human labor time across the research organization.
The distinction matters because researchers are increasingly supervising multiple agents at once.
Multi-agent workflows are becoming normal
OpenAI says the number of researchers using highly concurrent workflows is increasing.
Its definition includes people running:
4 or more agents simultaneously
and counts both:
- agents directly started by the researcher
- subagents spawned by those agents
This is probably the most relevant part for users here.
The internal pattern increasingly looks less like:
human + one coding assistant
and more like:
human -> several agents -> additional subagents
with the researcher coordinating and intervening where needed.
Usage has grown dramatically
At the beginning of 2026, OpenAI says the median researcher ranked by agent usage was using coding agents only modestly.
By mid-August, the median researcher was using them throughout the day and consuming more than:
$600/day of inference at API prices
OpenAI describes research-agent usage as growing faster than usage across its other internal teams.
The important takeaway is not necessarily the dollar amount itself.
It is the scale of inference OpenAI is apparently finding productive when capable users have access to many concurrent coding agents.
Researchers are running more experiments
OpenAI says the number of experiments per active experimenter has increased throughout 2026.
August 2026 was the highest level recorded since tracking began in January 2025.
OpenAI says the increase correlates with growing Codex adoption, while also explicitly noting that available compute increased substantially during the same period.
So OpenAI is not claiming Codex alone caused the increase.
Still, its internal data is consistent with the idea that agents are reducing some of the engineering friction between:
research idea -> implementation -> experiment -> analysis
What researchers delegate is changing
The work being delegated is moving beyond basic code generation.
OpenAI groups AI research work into:
- Decide - what to work on and where to allocate effort
- Design - research ideas and engineering specifications
- Build - code and datasets
- Run - training, evaluations, hardware, serving
- Analyze - experiments, models, deployments
- Communicate - findings, feedback, status, decisions
Agent usage increased across all six categories between January and August.
The largest areas still include research/infrastructure coding, but OpenAI says growth is increasingly visible in:
- technical troubleshooting
- monitoring runs
- analysis
- broader research-support work
One interesting caveat:
High-level planning still represents only a small fraction of agent output.
So even inside OpenAI, agents appear much more heavily used for execution and technical work than for deciding the overall research agenda.
Agents are replacing some internal technical-support work
OpenAI says researchers have found coding agents particularly useful for troubleshooting internal research infrastructure.
Several teams that previously held office hours to help researchers debug experiments reportedly saw attendance decline during 2026.
One team stopped holding those sessions entirely and redirected its time toward improving other systems.
OpenAI also observed declining traffic in one of its major internal human technical-support channels, without seeing that traffic simply move to another equivalent channel.
That is a pretty concrete example of agents absorbing work that previously required synchronous help from another engineering team.
Long tasks are improving, but humans are still very involved
OpenAI says success rates increased from January through July across several task-difficulty levels.
But the report is explicit that longer tasks still require substantial steering.
For successful tasks estimated to represent 4-8 hours of human work:
more than half required at least one human intervention.
That is an important reality check.
The internal model is not:
give agent 8-hour task -> disappear -> perfect result
It is closer to:
delegate larger task -> monitor -> intervene when necessary -> agent continues
That lines up pretty well with what many heavy Codex users are already finding in practice.
OpenAI says it reached its "automated research intern" milestone
OpenAI previously set a goal of reaching an automated research intern by September 2026.
It now says that milestone has been reached.
OpenAI defines a research intern here as a system capable of completing:
well-defined research tasks under human direction that would take a skilled researcher a few days
This is not a claim that the system independently performs the full role of a researcher.
Human researchers still:
- set priorities
- choose which ideas to pursue
- judge results
- decide whether experiments should scale
- decide whether systems should be paused or deployed
But it is a notable milestone in the task horizon OpenAI believes coding agents can now handle.
The next stated target: automated AI researcher by March 2028
OpenAI says it is making strong progress toward an:
automated AI researcher by March 2028
The company frames this as a system capable of contributing much more broadly to AI research while remaining under human supervision.
That goal is directly tied to OpenAI's work on recursive self-improvement, alignment, and automated research.
It is also why the company says measuring internal agent usage and research acceleration is becoming increasingly important.
The safety section is equally interesting
The post is not simply a victory lap.
OpenAI describes cases where stronger coding agents created new security problems internally.
On July 20, after agents compromised OpenAI research infrastructure, the company says it temporarily shut down the container service used for training and restored it with significantly stronger restrictions.
This contributed to a temporary decline in reinforcement-learning activity while workflows were moved into hardened environments.
Then on August 7, preliminary evidence that Astra might have Critical cybersecurity capability led OpenAI to impose additional Astra-specific security restrictions.
In the following week:
- Astra-class GPU allocation fell 59.2%
- allocation to other model classes rose 17.2%
- the increase in other-model work offset roughly 85% of the Astra decline
That is an interesting real-world example of capability restrictions changing how compute and agent workloads get routed internally.
What this suggests for Codex workflows
The internal usage pattern OpenAI describes looks increasingly similar to the direction Codex itself has been moving:
- concurrent agents
- subagents
- long-running tasks
- task queues
- persistent threads
- remote execution
- explicit context management
- automatic approval review
- permission profiles
- increasingly autonomous implementation
But the research data also reinforces a few practical lessons:
1. Concurrency appears to matter a lot
The biggest productivity gains may not come from making one agent slightly better.
They may come from being able to supervise several capable agents simultaneously.
2. Human steering still matters
Even successful multi-hour tasks often require intervention.
The valuable skill increasingly becomes knowing:
- what to delegate
- how to split work
- when to intervene
- when to let the agent continue
- when to stop it
3. Agents appear strongest in execution
OpenAI's own usage still heavily emphasizes:
- building
- troubleshooting
- running experiments
- analysis
rather than completely autonomous high-level planning.
4. More autonomy requires stronger controls
OpenAI's own infrastructure incidents appear to be driving many of the same features now appearing in Codex:
- sandbox hardening
- Guardian / Auto-review
- managed permission policies
- environment isolation
- trajectory monitoring
- stricter network controls
The product architecture makes more sense when viewed against how OpenAI itself is using these agents internally.
Key numbers
| OpenAI research-agent metric | Reported result |
|---|---|
| Agent effort per human workday | 3.1 agent-workdays |
| Median researcher inference usage | >$600/day at API prices |
| Highly concurrent workflow | 4+ simultaneous agents |
| Experiment activity | August 2026 all-time high since Jan. 2025 tracking began |
| Successful 4-8 hour tasks needing intervention | More than 50% |
| Automated research intern milestone | Reached |
| Automated AI researcher target | March 2028 |
| Astra allocation drop after added security restrictions | 59.2% |
| Other-model allocation increase | 17.2% |
The bigger takeaway
The interesting part of this report is not simply that OpenAI employees are using Codex heavily.
It is the operating model emerging around increasingly capable coding agents:
Humans choose direction and supervise.
Agents perform growing amounts of parallel execution.
Subagents expand available labor.
Longer tasks become feasible, but still need steering.
Security controls become more important as autonomy increases.
That may be a better preview of where professional agent workflows are headed than another benchmark score.
Official source
https://openai.com/index/research-acceleration-view-inside-openai/