Google's self-improvement paper adds a memory, not a flywheel
Self-Improvement Memory keeps a record of harness edits and buys 2.36 points on Terminal-Bench 4 at 19-22% absolute success. The Reddit framing claimed more.

On 18 November a post in r/singularity announced the Singularity, in capitals. Google researchers, it said, had demonstrated AI that improves its own software, remembers what worked, and carries those gains across model families — from Claude to Gemini, from one generation to the next — so that progress accumulates instead of starting over. The thread collected 672 points and 72 comments. What it did not collect was the size of the effect.
The paper underneath it, arXiv 2611.18856, is called Self-Improvement Memory Enables Continual Recursive Self-Improvement. Ten authors, split across Google Cloud AI, Google DeepMind and The Pennsylvania State University. Submitted 13 November, CC BY 4.0. Xin Yu, first author, notes the work was done while he was an intern at Google. The thread's description of the mechanism is defensible. Its description of the magnitude is not.
What the record actually contains
Nothing in this paper changes a model weight. What improves is the harness: the code, prompts, tool definitions and control flow wrapped around a policy model that stays frozen throughout. The authors work on something they call Continual Recursive Self-Improvement, which means resuming an existing harness-optimisation run after the benchmark changes or the policy model is swapped, as long as the executable interface stays compatible.
Their contribution is a data structure. Self-Improvement Memory groups selected harness edits by the recurring problem each one addresses, and stores four things per attempt: the rationale, the predicted outcome, the observed outcome, and its provenance — which domain, benchmark, policy and round produced it. The proposer and the selector then read that entire record, with no retrieval step and no truncation. New attempts get appended.
That is the whole of "remembers what worked". It is a log, organised by failure mode, that an LLM acting as a harness engineer reads end to end. The paper is unusually explicit that failed edits stay in it: every recorded attempt keeps its measured outcome, quote, "even when the edit regresses or fails to fix a predicted task". A memory that only kept successes would be a highlight reel; this one keeps the misses because the misses are the information.
Nineteen percent, plus two
The headline experiment is coding. Ten independent source runs from Terminus-2 on Terminal-Bench 2.1, each seeding two ten-round Terminal-Bench 4 runs with matched budgets. Mean held-out TB4 score lands at 19.33 without the memory and 21.70 with it, from a shared mean starting point of 18.36. Mean paired advantage is 2.36 points, 95% CI [1.05, 3.68], paired t(9) = 4.06, p = 0.003, signed-rank p = 0.006, dz = 1.28. SIM wins nine of ten pairs; the tenth favours no-SIM by 0.61.
The statistics are clean and the sample is small but honestly reported. The absolute numbers deserve the same attention. These harnesses solve roughly one task in five on Terminal-Bench 4. A two-point gain on that base is real and reproducible, and it is under three points off an 81.6 per cent failure rate — a long way from a flywheel that compounds its way out of the benchmark. Any reader who came away from the thread expecting a capability jump should sit with 21.70 percent for a moment.
Where the memory earns its keep
Two follow-up experiments matter more than the headline, because they test the thing the Reddit summary claimed.
Across six cross-dataset transitions with the policy held fixed, Full SIM finishes highest in all six, between 2.43 and 4.35 points above harness-only continuation. A stripped version that keeps only root-cause diagnoses ranges from 1.82 points below harness-only to 2.40 above. So the rationale and the recorded outcome carry value that the diagnosis alone does not — you cannot compress the record to "this class of bug is the problem" and keep the gain.
The cross-model result is stronger. Moving from Opus 5.5 to Gemini 3.8 Flash on the same benchmark and split, the Opus-evolved harness scores below Gemini's own seed harness in every single domain, by 0.60 to 5.48 points. Full SIM recovers in all four domains and beats harness-only continuation by 3.60 to 11.33 points. Agentic workspace is the outlier that justifies the excitement: both start at 68.41, the memory reaches 84.75, harness-only reaches 73.42.
Where carrying the record hurts
The paper's generation study is the detail a takeoff narrative cannot hold. Same benchmark, same seed, three conditions: seed, fresh recursive self-improvement, and continued from the previous generation.
| Policy | Seed | Fresh RSI | Continued (CRSI) |
|---|---|---|---|
| Gemini 2.5 Flash | 17.8 | 21.4 | 22.4 |
| Gemini 3.5 Flash | 70.2 | 73.3 | 76.8 |
| Gemini 3.8 Flash | 87.2 | 88.9 | 90.5 |
| Gemini 4 Argon | 89.7 | 95.6 | 94.8 |
Continuation wins in two of the three later generations and loses 0.8 points on Argon. A record of what worked against an older model is not automatically an asset against a newer one; on the strongest policy tested, it was slightly worse than starting clean. A second negative sits in the text-classification run: the evolved FewShotAll harness begins at 72.92 on the target, below its own seed's 75.72. Harness-only continuation crawls to 74.12 and never catches a cold start at 75.92, while Full SIM reaches 77.92. Source optimisation, in other words, does not guarantee a better starting point. Only the memory rescues that run.
The last check is about consolidation. Given one shared harness for three models, per-model harnesses score 75.20, a shared seed 73.28, sequential CRSI 74.20, and a unified synthesis drawing on feedback from all three 75.24. A single harness can match separately evolved ones. It does not beat them.
Who grades the improvement
Four domains carry the paper. Coding runs Terminal-Bench 2.1 into Terminal-Bench 4. Text classification goes from a three-dataset source suite to an eight-dataset target suite that never appears in source RSI. Agentic workspace moves from Harvey LAB to the equal-weight mean of JobBench, GDPval and APEX-Agents, judged by Gemini 3.8 Flash. Engineering design moves from EngDesign to Frontier-Eng under frozen verifiers. Evolve and held-out splits are roughly equal, and only evolve-set feedback reaches the proposer.
One of those four, the agentic workspace, is scored by an LLM judge from the Gemini line. Coding is pass@1, classification is accuracy, and the paper says outright that neither engineering metric uses an LLM judge; the cross-generation study also runs on Gemini policies. What the authors do concede is that workspace scores "may also reflect biases of the LLM judge". But the honest reading is that in this setting the same lineage of model proposes the edits and, in part, scores them. That is a reasonable way to run an experiment about harness engineering. It is not evidence about a system that can improve beyond its own judges.
What two points buys you
This is the most transferable result in the paper, and not the one that went viral. Because no weights move, the method applies to a model you do not own and cannot fine-tune — a hosted frontier API included. What you maintain is a text file and a loop.
The costs are equally plain. Reading the whole record with no retrieval means it competes for the same context budget as the task, and the paper does not report how that scales past ten rounds. The gains are also benchmark-shaped: a harness tuned on Terminal-Bench 2.1 is not a general agent, and the Argon regression shows a model swap can cost as easily as it pays.
What it establishes is narrower and more useful than the headline: continuity in harness optimisation is achievable, it needs an explicit record rather than a summary, and it is worth roughly two percentage points on a hard coding benchmark. What it does not establish is that any of this accelerates. A curve that plateaus at 21.70 percent is not one that has escaped its benchmark, and one regression on the newest model is enough to keep "recursive" descriptive rather than predictive.
Expect the technique to show up in agent frameworks before it shows up in model cards — eval-driven harness tuning with a persistent failure log is cheap, unglamorous and easy to bolt onto existing infrastructure. Expect the framing to outrun it, too. The gap between 672 points and 2.36 points is the whole story here, and the paper is the more interesting half.


