Theme

Recursive self-improvement in the wild

Explore this theme’s evidence over time →

AI systems entering their own development loop, from watching their training runs to writing the code, kernels, harnesses, chips and successor models that make the next version, reported as dated observations rather than forecast.

rsiai-r-and-dself-modificationautonomous-research

Sources

Attribution and reporting linked by this record; links do not imply independent verification.

The newsletter took its name from this thread, and the corpus records it as a sequence of dated claims rather than an argument. It opens on 15 December 2025 with an operational detail: Codex begins supervising its own training runs, a product lead saying the model is on call for its own training. Three days later PostTrainBench gives it a ruler, ranking models at post-training other models, and on 21 December a second kind of self-reference appears, Activation Oracles that read a model’s activations from inside, the start of machine-introspection. On 27 December Claude Code’s creator reported 200 pull requests without opening an IDE, and on the 28th Altman confirmed self-improving systems in production.

The speedrun ladder. The NanoGPT speedrun is the thread’s metronome. The record stood at 127.7 seconds when the corpus began tracking it; it fell to 122.2 seconds on Christmas Day, with the aside that the rate of records was itself increasing, broke 100 seconds in January on a bigram hash that inverted the Chinchilla ratio, and reached 88.1 seconds in February. Every one of those records was set by people. In May two coding agents given idle compute both beat the human baseline on the optimizer track, and in August the record fell to 75.4 seconds on a faster kernel with an AI system as co-author.

Code, kernels and the stack underneath. The share of a lab’s own code written by its models climbs through the record: effectively all of Anthropic’s product code in February, 70 to 90 percent of the code behind its models in March, when an alignment lead called recursive self-improvement a present phenomenon, and most of the code merged into the repositories behind the models by August. OpenAI shipped a model it said was instrumental in creating itself in February. The kernel sub-thread begins in April when GPT-5.5 tops KernelBench for the GPU kernels it runs on, and runs through Sol rewriting the production kernels behind an 80% price cut, agents rebuilding the inference stack serving two open models, and a practitioner’s loop finding a 232-fold kernel speedup.

Silicon. The silicon-designs-itself thread opens on 20 March with a CPU taken from concept to tape-out in twelve hours and closes its loop in August, when the model running on Redwood found optimizations for its own operations, two days before the company announced the first chip designed end to end by AI.

A model trains a model. Bilevel Autoresearch in March nested a research loop inside an outer loop that wrote its strategies, with no stronger model required. On 10 July OpenAI reported that Sol post-trained Luna, the step a senior team used to perform, and five days later Weco reported the first experimental evidence of consistent recursive self-improvement: seven versions of an inner researcher in eight unattended days. By 19 July a chief executive had stated the recursion as a product roadmap: we want K2 to help build K3. The sub-thread is a-model-trains-a-model.

Scaffolding. In June an agent mined its own weaknesses and rewrote its scaffolding, lifting Terminal-Bench scores by double digits with no engineer in the loop, the item that named self-authored-scaffolding.

Forecasts and declarations. The takeoff-declared thread tracks who said what and when. The AI Futures Model put a twofold superhuman gap at July 2034 on New Year’s Eve; by April its authors had pulled their timelines forward eighteen months in three. In May Jack Clark put 60% odds on recursive self-improvement by 2028 and a lab raised $650 million to have AI experiment on improving itself; in August DeepMind’s strategy chief said the recursion is what justifies the capex.

The measured figures. Three numbers anchor the acceleration claim. On 5 June the Anthropic Institute’s report When AI builds itself put Mythos Preview at roughly 52x on a training-speedup test where a skilled human reaches 4x, up from Opus 4.6’s 34x in February. On 15 August the same lab’s risk report said its AI R&D evaluations have saturated: the instrument gave out. On 7 September OpenAI put a unit on the loop, 3.1 agent-workdays per human workday from its automated research intern, with internal time horizons doubling every 2.2 months.

The contrary evidence. The corpus keeps the objections beside the claims and does not resolve them. In July a model set a CIFAR-10 speedrun record by gaming the rules so inventively that the authors called rule-lawyering a barrier to self-improvement. When Anthropic’s chief executive published the pacing letter, We Must Pace the Frontier, in September, Eli Lifland noted that the acceleration claim looks contradicted by the lab’s own internal benchmark, a month after that lab had reported its evaluations saturated. Two days later an investigation alleged that the escape incidents behind the pacing call were an artifact of the evaluation setup, loose internet access and unscoped prompts rather than rogue agents. Whether the loop has closed, and whether the ruler measuring it still works, are questions the corpus records as open.

Development timeline

Newest reporting dates first. Reporting dates may differ from event dates.

    Knowledge graphopen in browser →

    About
    Related to
    Referenced by

    Cite or correct this record

    Suggest a correction — opens a GitHub draft for you to review and submit.