OpenAI: AI agents now finish nearly half of multi-hour research tasks on their own
OpenAI has published new internal figures on how much AI agents are speeding up its own research. On tasks that would take a human two to four hours, agents now succeed without help 46 percent of the time. The report also shows where the agents still clearly fail and why humans remain essential.

What it's about
OpenAI has released its second report on what it calls research acceleration. In it, the company measures how much AI tools, especially coding agents, are changing the way its own research division works. Coding agents are AI systems that write code, run programs and hunt down bugs on their own. The report follows a first analysis from September and draws on internal measurements through mid-October 2026.
The short version: the agents now do far more work on their own than they did in the spring. But OpenAI describes the progress as "jagged." On some tasks the agents are very good. On others they usually fail, and humans remain a fixed part of the research process.
OpenAI frames the release in policy terms. It argues that AI labs should be required to disclose signs of recursive self-improvement (RSI). That's a process in which AI speeds up the development of the next generation of AI, which in turn speeds up the generation after that. OpenAI stresses that the report shouldn't be read as a sign that it is aiming for full RSI.
The report has three parts: research inputs (here, agent usage), the process (how researchers work) and outputs (how model capabilities improve).
How much the agents handle alone
The headline figure covers tasks the agent completes successfully without any human intervention. OpenAI groups tasks by how long they would take a human:
| Estimated human time | Success rate in March | Success rate in October |
|---|---|---|
| 2 to 4 hours | 23 % | 46 % |
| 4 to 8 hours | 13 % | 35 % |
OpenAI flags one caveat itself. Because the agents have improved, researchers may now be handing them different tasks than before. So the higher rate reflects not just better capabilities but also changing choices about what gets delegated.
The breakdown by task type tells you more. For this, OpenAI uses a taxonomy of AI research tasks developed by the research institute Epoch AI. From August 1 to October 18, 2026, the rates for the top-level categories were: communicating 69 percent, analyzing 58 percent, and building just 43 percent. At the level of individual tasks, the spread is even wider:
| Task | Success rate without intervention |
|---|---|
| Monitoring training runs for problems | 79 % |
| Answering technical questions | 72 % |
| Launching training runs | 35 % |
| Building evaluation, RL and agent environments | 29 % |
| Writing code for inference and serving systems | 25 % |
Inference and serving systems are the software that runs a finished model for users. RL stands for reinforcement learning, where a model learns through rewards. OpenAI warns that as long as performance is this uneven, the weak spots could become bottlenecks that hold back any strong overall acceleration.
Usage and costs are exploding
According to OpenAI, agent usage is growing exponentially. Measured at API list prices, meaning what a regular customer would pay for the same compute, the numbers look like this:
- Median researcher: around $2,400 per day in October, up from $1,500 in September (an increase of 62 percent).
- 90th percentile, the threshold for the heaviest ten percent of users: around $23,000 per day, up from $11,000 in September (an increase of 105 percent).
A footnote explains a dip in the data. A temporary efficiency change to the agent software starting August 21 sharply reduced measured usage. It was gradually rolled back from September 10, for reasons OpenAI says had nothing to do with cost. OpenAI researchers have no quotas on agent usage.
As a second metric, OpenAI introduces "agent workdays": eight hours of agent runtime count as one workday. Per researcher per calendar day, this figure rose from 0.5 to 5.7, an elevenfold jump. In the pretraining teams (a model's foundational training) and posttraining teams (the fine-tuning that follows), it was around eight. In scaling and infrastructure it was around four. Because the metric mainly captures interactive use, automated workflows are likely undercounted.
Many researchers also run several agents at once. By mid-October, more than two thirds of the researchers tracked had at least four agents running in parallel at their daily peak, and more than ten percent had at least sixteen.
In September 2026, the API-equivalent value of agent usage was roughly twice what the researchers were paid in salary, excluding equity. According to the report, though, equity makes up 70 to 80 percent of target compensation for OpenAI researchers. Even so, all internal use of Codex, ChatGPT and the API together accounts for only about 2 percent of OpenAI's total research compute.
What the researchers say
In a survey of 101 research staff in late August and early September, OpenAI asked: what would you give up to avoid losing every coding agent better than GPT-5.2 for three months? The median answers:
- 40 percent of team headcount
- 30 percent of the team's compute
- 50 percent of compute, if the question were asked in January 2027
Without agents, using only GitHub Copilot and ChatGPT, a team estimated it would need a median of three months to do one month's worth of work. OpenAI itself points out that self-reports can be inaccurate and that the sample wasn't drawn systematically. In a second, smaller survey in October, 27 of 28 respondents preferred the latest internal model over an experienced human research engineer paired with a 2024 model such as o1-preview.
When it comes to the big ideas, humans still see themselves ahead. For the models GPT-6 Astra and GPT-6.2 Astra, researchers consistently credited the most important ideas in posttraining and safety monitoring to humans, with the models helping to implement them. The exception was pretraining for GPT-6.2 Astra. There, ideas emerged in conversation with Codex: one researcher credited Codex with key insights, and another said their idea only worked well after Codex suggested a change.
Interviews with ten researchers paint a mixed picture. The agents speed up implementation dramatically. One safety researcher says setting up an evaluation, a testing procedure for models, now takes a day instead of up to two weeks. At the same time, the agents have "bad taste" in research ideas, code quality and data quality. They go down rabbit holes, produce "AI slop" (low-quality AI output) and make wrong assumptions in their analyses. One pretraining researcher puts it this way:
"I do think I have better taste in ideas. But I'm not at all confident that will stay true for long."
More code, more experiments, better models?
On the output side, OpenAI cites three metrics. Lines of code changed per active employee rose sharply in 2026 compared with the pre-2025 average, and tests aren't counted. The number of experiments per active experimenter in the four weeks to October 18 was 1.68 times the 2025 level. But both measure activity, not necessarily progress.
That's why OpenAI introduces the OpenAI ECI, an internal variant of the Epoch Capabilities Index. The index combines many benchmarks into a single overall score for a model's capabilities. According to OpenAI, the top score of its own models has risen by 16.4 points per year since August 2025. Epoch has observed a trend of 14 points per year since late 2024. That suggests a slight acceleration, though OpenAI concedes that its own models score better on the internal index than on Epoch's because of the different benchmark mix.
More effort on safety
To see what researchers actually work on, OpenAI automatically sorted Slack posts, code changes and internal documents from January to September 2026 into research areas. Safety and alignment, the work of making sure AI systems do what humans intend, saw the biggest absolute growth. Documented work-weeks rose 77 percent, driven by new hires and by existing researchers switching focus. The work includes alignment testing, monitorability and research into "reward hacking," where a model games its reward signals instead of actually solving the task. OpenAI sees a clear turning point after the "Hugging Face incident" in July 2026. The report doesn't explain what exactly happened.
The bigger picture
The report is one of the most detailed looks any major AI lab has given into how it works internally. It adds to similar disclosures: Anthropic has published three such reports, Google DeepMind tracks the growing share of AI-written code, and the evaluation organization METR worked with Anthropic to estimate how much internal Claude models speed up progress.
The numbers point in a clear direction. AI is already doing a large share of the routine work in AI research, and that share is growing fast. But you should read a lot of this with caution. All the data comes from OpenAI itself and hasn't been independently verified. The surveys rely on self-reports. The cost figures are list prices, not actual internal costs. And by OpenAI's own admission, the capabilities index favors its own models.
OpenAI itself warns that past trends don't allow reliable predictions. Sudden breakthroughs like the recent ones in mathematics could happen in deep learning too. The report raises one question but doesn't answer it yet: is AI accelerating the development of new capabilities faster than safety research? The answer will show how seriously the call for transparency about AI self-improvement is meant.
Sources
- Techmeme openai.com
- techtimes.com techtimes.com
- dev.to #ai dev.to
- Reddit r/singularity reddit.com
- Gigazine (JP) gigazine.net
- Naver News (KR) khan.co.kr
Ask the AI assistant
Questions about this article, installation or background? Our assistant knows this page and runs on our own machine, not in someone else's cloud.
The Assistant is an AI (Gemma 4) and can make mistakes – please check important details against the source. Questions are used only to generate an answer and are deleted after one hour. Please don't enter any personal data.
Comments
What do you think? Already tried it? Write it here, no sign-up needed.
Comments are public. Links aren't allowed, and we delete abusive posts. You can delete your own comment at any time in this browser. Learn more in the Privacy Policy.