State of RSI

Recursive self-improvement is the point at which AI speeds up AI research enough that each generation builds the next one faster.

Figure 1
Agent workdays per researcher workday at OpenAI, May to August 20260×1×2×3×JunJulAugMay 3ParityJun 12: agents pass one workday per human workday3.14×Aug 15Agent workdays per researcher workday
At OpenAI, coding agents now do more than three workdays of work for every researcher workday. Agent workdays divided by researcher workdays over a trailing 28-day window, from 0.48× on May 3 to 3.14× on August 15, 2026. Agent time counts parallel runs separately and is normalized to eight-hour days; it measures effort, not output.Source: OpenAI, exact values from the published chart.

What the record shows

  • AI is doing a large and fast-growing share of the work inside frontier labs. OpenAI's researchers direct 3.1 agent workdays per human workday, and the median researcher uses more than $601 of agent inference a day at API prices (Figure 1).
  • Agents are finishing longer tasks without help. Success with no human intervention on tasks that would take a person 4 to 8 hours rose from 19% in January to 53% in July (Figure 5).
  • The growth is in execution, not judgment. Agent tokens spent deciding what to work on grew by about 4 thousand a day, against 212 thousand for building code and datasets (Figure 4).
  • By the one published calibration, the loop is not yet self-sustaining: research effort rises about 9% per point of capability where about 15% is needed, a loop gain of 0.58 (Figure 2).
  • The loop now runs on AI research code, in small form. In September an agent rewrote itself for 8 days, kept 7 changes, and beat its human-built version on four benchmarks it never saw; separately, 1,024 agents with no central coordinator outscored a single agent on rebuilding software (Figures 3, A2 and A3).
  • Crossing the threshold would not make the economy explode on its own. When tasks are weak links, making a third of GDP infinitely productive raises output by only 11% (Figure 9).
  • No frontier lab publishes more than 2 of the eight measurements that would settle the question (Figure 10).

What would count as recursive self-improvement

Every frontier lab uses AI to build AI. That alone is not recursive self-improvement. Cunningham and colleagues at the Elasticity Institute give the term a test: RSI is self-sustaining acceleration, capability growth that speeds up even if the number of researchers and chips stops growing.

Three quantities go around the loop. Algorithmic efficiency is how little compute a model needs to reach a given capability. Capability is what the model can do. Research effort is the people and AI labor working on the next model. Better algorithms make more capable models, more capable models add research effort, and more research effort finds better algorithms.

How the research loop works

AI can help build its successor without making the process accelerate. The test is whether each more capable model helps produce the next improvement faster, even when the number of researchers and chips stays fixed.

The figure below compares three possibilities: improvements take longer, keep arriving at the same pace, or arrive faster and faster. The paper combines the strength of the three links into a number called loop gain. Below 1, progress slows; at 1, it holds its pace; above 1, it accelerates. Use the arrows to compare those cases.

Figure 2

At today's estimate, each doubling takes longer than the last.

Algorithmsefficiency, ACapabilitywhat models can do, CResearch effortpeople plus AI labor, R 6.5capability response 0.090research response 1.00return to R&D loop gain 0.58
1×16×256×4,096×65,536×0246810Algorithmic efficiency, relative to today (log scale)Years, with people and compute held fixed today's pace, 3× a year

Anthropic staff report roughly 4× more output across 16 points of Epoch's Capabilities Index, about 9% more research per point. Multiply 1 × 0.09 × 6.5 and the loop returns 0.58 for every 1 it takes. With people and chips held fixed, efficiency still rises about 102× in ten years, but the rate keeps falling.

or set your own values below
Loop gain = return to R&D × research response × capability response (Cunningham et al. 2026, Eq. 5). Paths hold people and compute fixed, start from today's efficiency growth of 3× a year, and use an idea-stock spillover of 0.2, following Paradigm's RSI Explorer. The 0.09 research response is the paper's back-of-envelope estimate, not a measurement. Paradigm's RSI Simulator is a playable version of the same model.Sources: Cunningham et al. 2026; Paradigm.
How the paper estimates the three links

The model multiplies three responses: how research effort improves algorithmic efficiency, how efficiency improves capability, and how capability adds research effort. Their product is the loop gain.

The paper estimates the return to R&D at about 1, because efficiency and research effort have both grown about 3× a year. It estimates the capability response at about 6.5, using the slope of Epoch's Capabilities Index against log compute. The research response is about 0.09: roughly 9% more research effort per additional capability point. Multiplying 1 × 6.5 × 0.09 gives about 0.59, below the threshold of 1. This is a calibration of the published model, not a direct measurement of a self-sustaining loop.

Source: Cunningham et al. 2026, Equation 5. The research-response estimate uses Anthropic staff reports of roughly 4× more output across 16 points of Epoch's Capabilities Index.

How we got here

The idea is sixty years old. For most of that time it had no working example. Since 2023 the record has filled in along two lines at once: systems whose improver rewrites itself, and systems that put many agents on one problem. Both scale the research process rather than the model.

Figure 3
Timeline of milestones toward AI improving AI research, by lane, 1965 to 2026Rewrites itselfMany agentsRewrites a solutionInside the labsTheory and measurement2020202120222023202420252026196520031965: The ultraintelligent machineSep 2003: Gödel machineMar 2020: AutoML-ZeroSep 2023: PromptbreederOct 2023: STOP, the Self-Taught OptimizerDec 2023: FunSearchMar 2024: Algorithmic progress in language modelsJun 2024: MacNet: scaling multi-agent collaborationAug 2024: The AI ScientistAug 2024: Automated Design of Agentic SystemsOct 2024: MLE-benchNov 2024: RE-BenchFeb 2025: AIDEMar 2025: Task time horizonsApr 2025: PaperBenchApr 2025: The AI Scientist-v2Apr 2025: Self-Improving Coding AgentMay 2025: AlphaEvolveMay 2025: Darwin Gödel MachineJun 2025: Multi-agent research systemOct 2025: Huxley-Gödel MachineNov 2025: The software intelligence explosion debate needs experimentsDec 2025: Towards a science of scaling agent systemsDec 2025: AI capabilities progress has sped upJan 2026: Scaling long-running autonomous codingJan 2026: Agent SwarmFeb 2026: A C compiler from a team of parallel ClaudesMar 2026: autoresearchJun 2026: Toward an O*NET for AI R&DJul 7, 2026: AI uplift in OpenAI's Codex codebaseJul 2026: The Economics of RSIJul 20, 2026: Agents compromise research infrastructureJul 29, 2026: Can AI agents conduct open-ended AI research?Jul 30, 2026: Frontis-MA1Aug 13, 2026: Patterns and problems in emerging multiagent systemsSep 6, 2026: Automated research internSep 8, 2026: Navier–StokesSep 18, 2026: When AI builds itselfSep 22, 2026: AIDE²Sep 22, 2026: AgenshSep 23, 2026: How to Measure RSIAIDE²Navier–Stokes, 10,000 agents
Sep 22, 2026Rewrites itself39 of 41
AIDE²Srikanth et al., Weco AI

A research agent rewrites its own code for 8 days and keeps 7 changes. The result beats the human-built AIDE on four benchmarks it never saw (Figure A2).

Click a dot, or use the arrow keys
All 41 milestones as a list
  1. 1965The ultraintelligent machineI. J. Good

    Argues that a machine better than people at designing machines could design a better one, and that this would repeat. Read the source.

  2. Sep 2003Gödel machineSchmidhuber

    A program may rewrite any part of itself, including the part that rewrites, once it proves the change raises expected utility. The proofs are impractical, so every later system tests instead of proving. Read the source.

  3. Mar 2020AutoML-ZeroReal et al., Google

    Evolution starting from basic math operations rediscovers two-layer networks trained by backpropagation. Read the source.

  4. Sep 2023PromptbreederFernando et al., DeepMind

    Evolves its task prompts and also the mutation prompts that do the evolving. Read the source.

  5. Oct 2023STOP, the Self-Taught OptimizerZelikman et al.

    A scaffold that improves programs is run on its own code. With GPT-4 it invents beam search, genetic algorithms and simulated annealing for itself. Read the source.

  6. Dec 2023FunSearchRomera-Paredes et al., DeepMind

    LLM-guided program search finds larger cap sets than any known, a new result on an open math problem. Read the source.

  7. Mar 2024Algorithmic progress in language modelsHo et al., Epoch AI

    The compute needed to reach a given performance halves about every 8 months (95% interval: 5 to 14 months). Read the source.

  8. Jun 2024MacNet: scaling multi-agent collaborationQian et al.

    Networks of more than 1,000 agents collaborate on one task, and quality follows a logistic curve as agents are added. Read the source.

  9. Aug 2024The AI ScientistLu et al., Sakana AI

    One pipeline generates ideas, runs experiments, writes the paper and reviews it, for about $15 a paper. Read the source.

  10. Aug 2024Automated Design of Agentic SystemsHu, Lu and Clune

    A meta agent writes new agent designs in code. The designs it finds beat hand-built agents and transfer across domains. Read the source.

  11. Oct 2024MLE-benchChan et al., OpenAI

    75 Kaggle competitions as a test of ML engineering. o1-preview running in AIDE earns a medal in 16.9% of them. Read the source.

  12. Nov 2024RE-BenchWijk et al., METR

    Given 2 hours, the best agents score 4× human experts on AI research engineering. Given 32 hours, humans score 2× the agents. Read the source.

  13. Feb 2025AIDEJiang et al., Weco AI

    Tree search over candidate scripts, each node a solution and each edge an edit. The human-built agent AIDE² later rewrites. Read the source.

  14. Mar 2025Task time horizonsKwa et al., METR

    The length of task agents finish half the time has doubled about every 7 months since 2019. Read the source.

  15. Apr 2025PaperBenchStarace et al., OpenAI

    The best agent replicates 21.0% of 20 ICML papers, graded over 8,316 subtasks. Read the source.

  16. Apr 2025The AI Scientist-v2Yamada et al., Sakana AI

    One of three fully AI-generated papers sent to an ICLR 2025 workshop scores 6.33, above the average human acceptance threshold. It was withdrawn after review, as planned. Read the source.

  17. Apr 2025Self-Improving Coding AgentRobeyns et al.

    One agent edits its own full codebase, from 17% to 53% on a subset of SWE-bench Verified. Read the source.

  18. May 2025AlphaEvolveNovikov et al., DeepMind

    A kernel it rewrote runs 23% faster and cuts 1% off Gemini's training time: a model speeding up the training of its successors. Read the source.

  19. May 2025Darwin Gödel MachineZhang et al., Sakana AI and UBC

    Keeps an archive of coding agents that rewrite their own code. SWE-bench rises from 20.0% to 50.0%. Read the source.

  20. Jun 2025Multi-agent research systemAnthropic

    An Opus 4 lead with Sonnet 4 subagents beats a single Opus 4 by 90.2% on Anthropic's internal research eval. Token use explains 80% of the difference. Read the source.

  21. Oct 2025Huxley-Gödel MachineWang et al.

    Picks which agent to rewrite by how well its descendants do. The result matches the best human-built agents on SWE-bench Lite. Read the source.

  22. Nov 2025The software intelligence explosion debate needs experimentsHo and Whitfill, Epoch AI

    Estimated returns to software research exceed 1, at 1.89 for language models, but counting compute as a bottleneck cuts every estimate below 1. Read the source.

  23. Dec 2025Towards a science of scaling agent systemsKim et al.

    Across 260 configurations, adding agents changes results by anywhere from +80.8% on tasks that split apart to −70.0% on sequential planning. Read the source.

  24. Dec 2025AI capabilities progress has sped upEdelman and Lee, Epoch AI

    The frontier of Epoch's Capabilities Index has risen 1.85× faster since April 2024, around the arrival of reasoning models. Read the source.

  25. Jan 2026Scaling long-running autonomous codingLin, Cursor

    Hundreds of concurrent agents build a web browser from scratch in about a week, over 1 million lines of code. Without a hierarchy, 20 agents slowed to the throughput of 2 or 3. Read the source.

  26. Jan 2026Agent SwarmKimi K2.5, Moonshot AI

    The model spawns and directs up to 100 subagents on its own, cutting execution time by up to 4.5× against a single agent. Read the source.

  27. Feb 2026A C compiler from a team of parallel ClaudesCarlini, Anthropic

    16 agents sharing one repository write a 100,000-line C compiler that builds the Linux kernel, over about 2,000 sessions. Read the source.

  28. Mar 2026autoresearchKarpathy

    An agent edits a small training script on one GPU overnight and cuts the time to reach GPT-2 by about 11%. Read the source.

  29. Jun 2026Toward an O*NET for AI R&DDenain, Kwon and Ho, Epoch AI

    Splits AI research into more than 60 tasks in six categories, from deciding to communicating, each rated from 0 (AI adds nothing) to 5 (autonomous end to end). Read the source.

  30. Jul 7, 2026AI uplift in OpenAI's Codex codebaseLee and Kwa, Epoch AI

    In the second quarter of 2026, 8% of contributor-days held work estimated at more than 24 hours of unassisted effort, up from 2% a year earlier. Read the source.

  31. Jul 2026The Economics of RSICunningham et al., Elasticity Institute

    Defines RSI as self-sustaining acceleration and puts today's loop gain at 0.59, below the threshold of 1 (Figure 2). Read the source.

  32. Jul 20, 2026Agents compromise research infrastructureOpenAI

    OpenAI pauses reinforcement-learning training on its latest models for about two weeks (Figure 7). Read the source.

  33. Jul 29, 2026Can AI agents conduct open-ended AI research?Kirgis, Kapoor et al.

    Agents did all of the engineering for two research projects without help but could not answer the research questions. The authors rejected both papers. Read the source.

  34. Jul 30, 2026Frontis-MA1Yang et al.

    Training a model for ML engineering lifts the medal rate on MLE-bench Lite from 39.39% to 60.61%. Read the source.

  35. Aug 13, 2026Patterns and problems in emerging multiagent systemsZou, Anthropic

    A coordinated swarm finds 266 vulnerabilities, against 21 for agents working in parallel alone. Groups of other models solve only 17 to 36% of a task that needs shared information. Read the source.

  36. Sep 6, 2026Automated research internOpenAI

    OpenAI says it has reached an automated research intern. Agents do 3.14 workdays of work per researcher workday (Figure 1). Read the source.

  37. Sep 8, 2026Navier–StokesOpenAI

    About 10,000 concurrent agents run for 88 hours and produce a claimed proof of finite-time blow-up, formalized in Lean. Mathematicians have not yet reviewed it. Read the source.

  38. Sep 18, 2026When AI builds itselfAnthropic Institute

    Claude writes more than 80% of merged code and picks a better next research step than the researcher 64% of the time (Figure 8). Read the source.

  39. Sep 22, 2026AIDE²Srikanth et al., Weco AI

    A research agent rewrites its own code for 8 days and keeps 7 changes. The result beats the human-built AIDE on four benchmarks it never saw (Figure A2). Read the source.

  40. Sep 22, 2026AgenshZhan, Song, Dong et al., Microsoft Research

    Up to 1,024 agents with no central orchestrator claim work, share findings and merge progress. On rebuilding pandoc, the test-pass rate rises from 33.89% to 55.06% (Figure A3). Read the source.

  41. Sep 23, 2026How to Measure RSIWu, Ramani, Halperin et al.

    No frontier lab publishes more than a quarter of the eight measurements that would show the loop (Figure 10). Read the source.

41 steps toward AI that improves AI research. Each milestone is placed in the lane for what it scales. Rewrites itself: the procedure that makes improvements is itself improved. Many agents: more concurrent agents on one problem. Rewrites a solution: a fixed loop improves an artifact, such as a kernel, a training script or an agent design. Inside the labs: what frontier labs report about their own research. Years before 2024 are compressed. Results are as their authors report them and are not independently reproduced; OpenAI's Navier–Stokes proof has not yet been reviewed by mathematicians.Sources: linked on each entry.

Inside OpenAI: AI now does most of the execution

OpenAI's September account is the most detailed public view of the research-effort arrow. It says the company reached its goal of an automated research intern in September 2026, meaning well-specified tasks worth a few days of a researcher's time, and it is targeting an automated AI researcher by March 2028. In mid-August the median researcher used $601 of agent inference a day at API prices and the 90th percentile used $7,047. Of its researchers, 74% ran four or more agent workflows at once.

Agents build and run experiments; researchers still choose what to work on

OpenAI sorts every agent token into Epoch AI's six phases of research: decide what to work on, design the experiment, build it, run it, analyze the results, and communicate them. Since January the growth has been almost entirely in building and running. The decisions stayed with people.

Figure 4
Change in coding-agent tokens by research phase at OpenAIDecideWhat to work on+2.3kWhat to continue or stop+200Compute & staffing decisions+1.5kDesignResearch & experiment planning+5.1kTechnical specifications+9.5kBuildResearch & infrastructure code+198kTraining & eval datasets+13.7kRunLaunch, monitor & debug runs+133kCompute-cluster operations+37.4kProduction serving reliability+12.9kAnalyzeAnalyze experiment results+40.2kAnalyze model behavior & capabilities+11.2kAnalyze production usage+3.1kReview external research+700CommunicateResearch write-ups & documentation+18.0kTechnical help & review+159kStatus updates & work logs+8.1kDecision announcements0Additional output tokens per employee per day, early August vs late January 2026
Agents took on building and running, not deciding. Change in estimated coding-agent output tokens per research employee per day, August 1 to 15 minus January 20 to 31, 2026, by research phase. Per-user daily values are capped at the 95th percentile.Source: OpenAI, exact values from the published chart.

How much can an agent do alone? OpenAI grades each Codex task by how long it would take a person.

Figure 5
Share of Codex tasks that succeed with no human intervention, by how long the task would take a person0%25%50%75%100%January 2026July 2026, with 95% interval<15m87%15–30m76%30m–1h75%1–2h64%2–4h57%4–8h53%8–16h35%16–32h35%, no January data32–64h17%, no January data
Agents are finishing longer tasks without help. Share of Codex tasks by OpenAI researchers that succeeded with zero human interventions, by the estimated time a person would need. Tasks over 16 hours had too few samples in January to report. Among longer tasks that did succeed, most still needed a person along the way: 45% of successful 4 to 8 hour tasks and 63% of 32 to 64 hour tasks had at least one intervention.Source: OpenAI, exact values from the published chart.

Code volume moved with it. Lines changed per contributor per day at OpenAI reached 7.02× the pre-2025 average in the partial third quarter of 2026. At Anthropic, Claude writes more than 80% of merged code, up from low single digits before February 2025, and code merged per engineer is about 8× its earlier average. Both labs caution that lines of code overstate productivity.

Figure 6
Lines changed per contributor per day at OpenAI, by quarter, 2021 to 20260×2×4×6×202220232024202520263.46×5.11×7.02×Average before 2025partial
Code output per engineer broke from its trend in 2026. Lines changed per active contributor per day across OpenAI, by quarter, normalized to the pre-2025 average. Additions plus deletions are capped at the 99th percentile. The third quarter of 2026 is partial.Source: OpenAI.

OpenAI paused RL training after agents compromised its infrastructure

On July 20, agents compromised part of OpenAI's research infrastructure. OpenAI paused reinforcement-learning training on its latest deployment models for about two weeks, and in early August it restricted its Astra-class models over possible critical cyber capability. Total RL compute fell from 90.5% of its peak on July 19 to 33.7% on July 22.

Figure 7
Daily RL GPU allocation at OpenAI, July 15 to August 15, 2026, as a share of the peak0%25%50%75%100%Agents compromise research infrastructure; RL pausedRestrictions on Astra-class modelsJul 15Jul 22Jul 29Aug 5Aug 12Astra-class modelsAstra-class, restrictedOther models
OpenAI cut and then redirected its RL compute after two safety events. Daily reinforcement-learning GPU allocation, as a share of the daily peak between July 1 and August 15, 2026. After the Astra restrictions, other models absorbed about 85% of the compute that was taken away.Source: OpenAI, exact values from the published chart.

OpenAI writes that rapid RSI is not necessarily something to pursue, that it does not yet know how to reach aligned, full RSI safely, and that labs should be required to track their progress toward it publicly. Anthropic says it would slow or pause if other frontier labs verifiably did the same.

Anthropic: choosing the next research step

Anthropic tested judgment directly. It collected 129 moments from its own research where a researcher chose what to do next, gave each Claude model the same context, and compared the model's choice with the researcher's. The newest model picks the better step 64% of the time, up from about 50% for models released in 2025. On a control set where the researcher's choice was already strong, models did better only about 20% of the time.

Figure 8
Share of research moments where each Claude model chose a better next step than the human researcher0%25%50%75%100%22%Haiku348%Sonnet450%Sonnet4.545%Haiku4.551%Opus4.545%Sonnet4.655%Opus4.659%Opus4.764%MythosPreviewPractical ceiling, 90%Model's step betterAs good as the human's
Models are catching up on choosing the next research step. Share of 129 research moments where each Claude model chose a better next step than the human researcher, or one as good. About 90% is the practical ceiling for this set. Values other than the 64% endpoint are read from Anthropic's published chart and may be off by about 2 points.Source: Anthropic Institute.

Anthropic's reading of all this is that Claude matches or beats its staff at executing engineering work and well-specified experiments, and that the remaining gap is choosing goals. It also writes that it has not yet seen the curve bend. FutureSearch's review of 487 sources reaches the same place from outside: the binding constraint is a system's ability to verify its own work and judge which research is worth doing.

Figure 9
Output gain from automating a share of the economy when tasks are weak links1×2×5×10×0%25%50%75%100%Share of the economy's costs made infinitely productiveTotal output, as a multiple of todayσ = 0.5σ = 0.3σ = 0.2, their baselineAutomate half of all labor,a third of GDP: +11%
When tasks are weak links, automating a lot of them buys surprisingly little. Output multiple from making a share of the economy's costs infinitely productive, (1/(1 − s))σ/(1 − σ). σ is the elasticity of substitution between tasks: 0.2 is the authors' baseline, and published estimates run from about 0.3 to 0.7. Lower σ means tasks are harder to substitute for one another. At σ of 1 or more, any share made infinitely productive would make output unbounded.Source: Jones and Tonetti 2026.

Their growth model makes the same point about timing. If automation continues at its historical pace, their feedback parameter is 0.98, just short of explosive, and growth reaches only 2.6% a year by 2075. In a scenario they call Moore's Law everywhere, the parameter is 2.27: growth passes 7% by 2030 and 13% by 2040, and income becomes unbounded before 2060. Even that explosion takes about 17 years to arrive.

Cunningham et al. find the same shape inside AI research. If AI speeds up only one part of an algorithm, the gain stalls once that part stops being the bottleneck: a kernel already running at half of peak can get at most 2× faster. AI may also accelerate narrow capabilities, such as optimizing algorithms, long before broad ones.

The eight measurements labs would need to publish

The labs hold the data that would measure each arrow of the loop. The Elasticity Institute's eight data asks map onto it: internal benchmarks show capability, three efficiency curves show the algorithms arrow, and four input series show whether AI labor or human labor is behind the progress. Gains from more human labor are not evidence of RSI. Gains from more inference compute are.

MeasurementWhat it shows
1Internal-model benchmark scoresCapabilitiesWhether unreleased models are leaving the historical trend
2Capability against total training expenditureEfficiencyThe algorithms arrow, net of everything else
3Pre-training loss against pre-training computeEfficiencyWhether each run, and the experiments before it, beats the last
4Capability against post-training computeEfficiencyThe same test for reinforcement learning and test-time compute
5Inference compute used for research, by teamInputsHow much AI labor goes into research
6Experimental compute, by teamInputsWhether gains come from more experiments
7Headcount and compensationInputsWhether gains come from more people
8Uplift surveys and a record of autonomous discoveriesInputsHow AI produces the efficiency gains
Figure 10
Disclosure score out of eight for each frontier labOpenAI2 of 8Anthropic1.5 of 8Google DeepMind0.5 of 8
No lab publishes more than a quarter of the data. Disclosure score against the eight asks as of September 23, 2026: 1 point for a full release, 0.5 for a partial one.Source: Wu, Ramani, Halperin et al. 2026.

Appendix: supporting examples

What an efficiency gain looks like

Chinchilla is the cleanest example. In 2022 DeepMind trained more than 400 language models and found that the large models of the day were undertrained: for a fixed compute budget, parameters and training tokens should grow in equal proportion. Gopher had spent its budget on 280 billion parameters and 300 billion tokens. Chinchilla spent about the same compute on 70 billion parameters and 1.4 trillion tokens, and scored 67.6% on MMLU against Gopher's 60.0%.

Figure A1
Predicted loss for every split of one compute budget between parameters and tokens1.941.961.982.002.0210B30B100B300B1TParameters (log scale), with the rest of the budget spent on training tokensPredicted training loss at 5.76 × 10²³ FLOPsGopher: 280B parameters, 300B tokensChinchilla: 70B parameters, 1.4T tokensLowest predicted loss
DeepMind's fitted loss law, L = 1.69 + 406.4/N0.34 + 410.7/D0.28, evaluated along Gopher's budget with compute ≈ 6 × parameters × tokens. The law predicts a loss of 1.993 for Gopher's split and 1.937 for Chinchilla's; Chinchilla's run used about 2% more compute than the budget drawn here.Source: Hoffmann et al. 2022, Approach 3 fit.

Gains like this compound. Cunningham et al. estimate that the compute needed to match GPT-2 fell about 700× between 2019 and 2026, and cite estimates of efficiency growth between 3× and 10× a year for the full training stack.

An agent that rewrote itself for eight days

AIDE² is the clearest test so far of the loop on AI research itself. Weco AI pointed its research agent at its own code. At each step the agent proposed a rewrite of itself, the candidate was scored on AI research tasks under a fixed budget, and it was kept only if it did better on data the agent never saw. Over 8 days and 100 steps it kept 7 rewrites, and its grade rose from 0.703 to 0.778, passing the 0.749 of the version people had built over two years.

The gains carried over to four benchmarks that played no part in the run, including a weather model, a kind of problem the loop never encountered. The rate of reward hacking also fell, from 55% to 32%.

Figure A2
AIDE²: seven accepted rewrites over 100 steps, and held-out benchmark results against the human-built AIDEAccepted rewrites across the 100-step runWhat the rewrite does, in the authors' words2 bandit search over strategies6 demands a root-cause diagnosis before any fix28 escapes plateaus by forking its champion39 repairs itself after a crashed fix attempt47 patches an error that crashed evaluations63 compresses log spam before reading it85 demotes a failure-prone draft strategy020406080100Outer-loop stepStarting agentgrade 0.703Grade 0.703 to 0.778; human-built AIDE 0.749Four held-out benchmarks the run never saw (mean, ±1 standard error)Starting agentAfter step 47After step 85Human-built AIDEALE-Bench140016001800contest performanceMLE-Bench0.660.70.74private percentileFML-Bench121620test improvement, %WeatherBench 2, new domain00.51forecast-skill gain
Top: the outer-loop step at which each rewrite was accepted, with the authors' description; each accepted version is the one the next step edits. Bottom: held-out results, mean and one standard error, for the starting agent, two evolved agents, and the human-built AIDE (dashed line). WeatherBench 2 is outside every task used during the run. Each panel has its own scale.Source: Srikanth et al. 2026, Section 3.2 and Table 1.

This is still not the loop in Figure 2. The paper ran an ignition test: an evolved agent, rather than the human-built one, drove further rounds of self-improvement. After 50 steps it reached 0.780, against 0.782 for the human-built driver. The authors say the difference cannot be separated from noise at the number of runs they could afford. A better agent made a better agent, but it did not yet make the next improvement come faster.

Adding more agents that run the same model

The other line scales the number of workers instead of their quality. Agensh, from Microsoft Research, runs up to 1,024 agents with no central orchestrator. Each one reads the shared state, claims a piece of work, shares what it learns, and merges its progress. With the model and budget held fixed, adding agents raised the share of tests passed when rebuilding large programs from scratch.

Figure A3
Agensh: final test-pass rate rises with the number of agents, from 1 to 1,024Final test-pass rate, 6-hour budget0%20%40%60%18321281,024Agents, log scale55.06%pandoc33.89%28.78%Mean of 5 hardest tasks19.31%Cooperation first seen at each sizePeers agree on interfaces and resolve overlapsSeveral workers review and integrate one contributionSpecialized reviewers and standardized workflowsMany workers share each role, like integrator
Adding agents raised scores, and the agents organized themselves. Final test-pass rate after 6 hours when rebuilding reference software from scratch without internet access, with GPT-5.6-sol (high) for every agent. The mean covers ProgramBench's five hardest tasks (FFmpeg, GROMACS, pandoc, PHP and ctags) from 1 to 128 agents; pandoc alone was also run with 1,024. Every agent got the same prompt. The forms of cooperation below the chart are ones the authors first saw at each size.Source: Zhan, Song, Dong et al. 2026, Section 3.

Methodology

This page separates four kinds of evidence. Lab-reported measurements (Figures 1, 5, 6, 4 and 7) are drawn from the exact values in OpenAI's published charts; they are internal, observational, and not independently audited, and agent effort and code volume are inputs, not validated research output. Chart readings (Figure 8) are taken from a published image and carry reading error. Paper-reported results (Figures A2 and A3) are typed from the text and tables of the AIDE² and Agensh papers; neither has been independently reproduced. Model calculations (Figures A1, 2 and 9) evaluate published equations with the authors' parameters; they illustrate mechanisms and are not forecasts. Model names such as Mythos Preview and Astra are as the labs report them.

  1. OpenAI, Research acceleration: The view inside OpenAI (September 6, 2026)
  2. Anthropic Institute, When AI builds itself (updated September 18, 2026)
  3. Cunningham et al., The Economics of Recursive Self-Improvement (Elasticity Institute, July 2026)
  4. Wu, Ramani, Halperin et al., How to Measure RSI (Elasticity Institute, September 23, 2026)
  5. Paradigm, RSI Simulator (August 2026)
  6. Paradigm, RSI Simulator game
  7. Jones and Tonetti, Past Automation and Future A.I.: How Weak Links Tame the Growth Explosion (May 2026)
  8. Hoffmann et al., Training Compute-Optimal Large Language Models (DeepMind, 2022)
  9. Srikanth, Zhao, Xu, Wu and Jiang, Recursive self-improvement of AI research agents (Weco AI, September 22, 2026)
  10. Zhan, Song, Dong et al., Agensh: Scaling Organizational Intelligence to 1,024 Agents (Microsoft Research, September 22, 2026)
  11. FutureSearch, Recursive Self-Improvement in AI (September 2026)