Papers
Topics
Authors
Recent
Search
2000 character limit reached

RRSI: Regularized Recursive Self-Improvement of Agent Harnesses

Published 21 Sep 2026 in cs.LG, cs.AI, and cs.CL | (2609.24972v1)

Abstract: An LLM agent's capability is largely magnified by its harness, namely the prompts, control flow, tooling, memory, and context management surrounding the frozen backbone model. Recent methods increasingly automate this process by iteratively proposing and selecting component-wise edits of an agent harness, practically establishing a form of recursive self-improvement (RSI) at the agent-system level. However, such recursive evolution may overfit by memorizing the training tasks, showing large in-distribution gains that shrink or even vanish on out-of-distribution benchmarks. We introduce Regularized Recursive Self-Improvement of Agent Harnesses (RRSI), which incorporates the principles of regularizations into harness self-improvement by constraining the evolution candidate proposal and selection. The proposer operates with a temporally annealed budget, limiting how many edits a candidate can bundle, and it encourages unexplored trajectories based on evolution history. The selector is equipped with a critic and a pruner: the critic screens benchmark-specific proposals, while the pruner, removes changes that are too small, too expensive, or no longer useful. Together these constraints favor reusable agent mechanisms over benchmark-specific ones or even noises. Across eight benchmarks spanning coding, agentic workspace and engineering design tasks, RRSI gains up to 14.1 points on the split it evolves against and up to 4.7 points on the five out-of-distribution benchmarks, while producing a harness that runs on 30% fewer policy tokens than the unregularized evolution. Code is available at https://github.com/google-research/rrsi and project page is https://regularized-rsi.com/.

Summary

  • The paper successfully demonstrates Regularized Recursive Self-Improvement as a method to improve agent harness evolution and transferability to unseen benchmarks.
  • RRSI enhances harness evolution by limiting adaptive overfitting and using mechanisms such as annealed edit budgets and structured exploration to perform targeted improvements.
  • When compared to various harness-evolution baselines, RRSI shows superior performance in retention of improvements across held-out benchmarks even when trained in domains such as coding, agentic workspace, and engineering design.

Problem formulation and motivation

RRSI: Regularized Recursive Self-Improvement of Agent Harnesses” studies recursive self-improvement at the agent-system level rather than at the level of model weights (2609.24972). The central object is an agent A=(π,H)A=(\pi,H) consisting of a frozen backbone policy π\pi and a harness HH. The harness includes prompts, control flow, tool interfaces, memory, skills, context management, output plumbing, and subagent orchestration. Harness evolution treats HH as the optimization variable: the system executes the current harness on an evolution set, analyzes trajectories and scores, proposes source-level modifications, evaluates candidate harnesses, and retains a candidate according to an empirical selection rule.

The paper’s central claim is that ordinary harness evolution is vulnerable to adaptive overfitting. The same finite evolution set is repeatedly reused to generate feedback, propose modifications, and select the next incumbent. Consequently, the evolution process performs adaptive empirical optimization over a highly expressive search space. Improvements may therefore arise from benchmark-specific behavior, stochastic evaluation effects, or unnecessary increases in inference-time computation rather than from reusable agent mechanisms.

This distinction is empirically consequential. The paper reports that several existing evolution methods obtain strong gains on their evolution split but retain little of those gains on held-out benchmarks; some perform worse than the initial harness after transfer. The authors consequently define generalization as the ability of an evolved harness to transfer to unseen benchmarks with different task descriptions, tool interfaces, and verifiers.

RRSI addresses this problem without restricting the set of harness components that may be modified. Prompts, control flow, tools, memory, skills, context management, and subagents remain editable. Instead, RRSI regularizes the trajectory through the harness search space by controlling both candidate proposal and candidate acceptance.

Figure 1

Figure 1: Evolution-set gains from prior methods often fail to transfer, whereas RRSI preserves improvements across held-out coding, workspace, and engineering benchmarks.

Method: regularizing the search trajectory

The paper distinguishes the potential edit space from the process used to traverse it. Let Ω(H)\Omega(H) denote all harnesses reachable through arbitrary source edits. RRSI leaves Ω(H)\Omega(H) open and imposes constraints on how proposals are generated and which proposals are allowed to become persistent harness state.

This design is important because a conventional restriction on the edit space could exclude precisely the structural changes that make an agent more capable. RRSI instead applies regularization to the adaptive search process. Its proposal-side mechanisms regulate search capacity and exploration; its selection-side mechanisms regulate evidence, leakage, stability, complexity, and structural sparsity.

Figure 2

Figure 2: RRSI constrains proposal capacity and selection criteria while preserving an open harness edit space.

Proposal-side regularization

The first proposal-side mechanism is an annealed edit budget. Early evolution rounds permit several independently attributable edits in a candidate, allowing the system to discover coordinated mechanisms. Later rounds progressively reduce the budget, eventually permitting only sparse updates. The schedule is cosine-annealed from an initial maximum to a minimum of one edit. The authors describe this as an L0L_0-style constraint, but explicitly clarify that it is not optimization of an L0L_0-penalized objective over a fixed parameter vector. It is instead a cardinality constraint on discrete harness edits in each update.

The second mechanism is evidence-aware credit assignment. Each evaluated candidate is recorded with its edited component, underlying hypothesis, source diff, measured score change, token-cost change, and acceptance outcome. Later proposals condition on this history. Rejected mechanisms remain available as negative evidence, while accepted mechanisms retain explicit credit. This is intended to reduce repeated testing of hypotheses that have already failed and to improve attribution as the edit budget becomes sparser.

The third mechanism is structured exploration. When performance stagnates within an empirically estimated noise band, RRSI reserves part of the proposal budget for components that have not yet been exercised. The editable vocabulary includes prompts, control flow, configuration, output plumbing, context management, client tools, skills, memory, and subagents. This exploration policy functions as a targeted diversity mechanism: it discourages collapse onto a narrow family of edits, such as repeatedly rewriting prompts while leaving structural mechanisms untouched.

Finally, proposal-side pruning identifies components that have produced no strictly positive measured gain over a recent window and presents them as deletion targets. This is described as analogous in role to L1L_1 sparsification: unproductive discrete structure is removed from the retained harness rather than merely tolerated.

Selection-side regularization

RRSI applies a leakage critic before full candidate evaluation. The critic rejects diffs that encode task names, entities, task-specific values, answers, or benchmark-specific logic, as well as inert machinery. The method does not reject generic improvements to prompts, tools, or control flow; its target is task-specific content rather than particular component types. Screening before evaluation prevents a leaking candidate from receiving an inflated evolution-set score that could influence subsequent search.

The selector also estimates an empirical noise tolerance δ\delta by repeatedly evaluating the unchanged base harness. A candidate must satisfy a noise-adjusted floor relative to the best observed score. This prevents the evolution path from drifting through a sequence of small regressions that individually appear compatible with stochastic variation.

Candidates that exceed the noise band must satisfy a gain-dependent cost rule. If π\pi0 is the candidate’s measured score improvement and π\pi1 its relative policy-token increase, acceptance requires that additional inference cost remain below a baseline allowance plus a term proportional to π\pi2. The resulting rule permits greater computation only when the measured gain justifies it. The paper calls this Ridge-like complexity control, while carefully noting that it is not a squared-norm penalty.

Candidates whose measured gain lies within the noise band are evaluated using a shaped admissibility rule incorporating score change, cost change, and structural novelty. In coding experiments, within-band score increases receive no direct credit; such candidates must instead reduce cost or introduce previously unused structural mechanisms. Engineering-design evolution additionally uses non-compensatory guards on valid-output rate and no-submission rate, preventing a primary-score gain from offsetting substantial degradation in execution reliability.

The final selector chooses the highest-scoring candidate among those that pass leakage screening, the noise-adjusted floor, the relevant cost or novelty rule, and any domain-specific guards. If no candidate is admissible, the incumbent remains unchanged.

Experimental design

RRSI is evaluated across eight benchmarks and three domains:

Domain Evolution benchmark Held-out or OOD benchmarks
Coding Terminal-Bench 2.1 SWE-bench Verified
Agentic workspace Harvey LAB Harvey LAB held-out, JobBench, GDPval, APEX-Agents
Engineering design EngDesign Frontier-Eng

The experiments use a frozen Claude Opus 4.8 policy for the primary evaluation. The proposer, trajectory analyst, and leakage critic also use Claude Opus 4.8. The coding environment contains 89 Terminal-Bench tasks, while Harvey LAB uses a fixed 120-task evolution split and 40-task in-distribution held-out split. EngDesign contains 61 tasks and is evaluated with deterministic task-specific simulators or testbenches. The OOD benchmarks introduce different task distributions, tool ecosystems, and evaluation procedures.

The comparison includes the unevolved harness π\pi3 and four harness-evolution baselines: Meta-Harness, AHE, TTHE, and HarnessX. All methods begin from the same base harness, use the same frozen policy, evolve on the same split, and receive the same candidate budget. This design isolates the effect of RRSI’s proposal and selection rules, although the evaluation remains dependent on the particular backbone, evolution budget, and hyperparameter choices.

Main empirical results

RRSI improves every reported held-out split. On the evolution benchmarks, it gains 6.0 points on Terminal-Bench 2.1, 4.9 points on EngDesign, and 1.1 points on Harvey LAB. The more important result is transfer: RRSI improves SWE-bench Verified by 1.8 points despite never being evolved against repository-level bug-fixing tasks; it improves the Harvey LAB held-out split by 2.3 points; it gains between 3.5 and 4.7 points on JobBench, GDPval, and APEX-Agents; and it improves Frontier-Eng by 4.3 Medal points, corresponding to a 24.3% relative improvement.

Figure 3

Figure 3: RRSI’s primary results across coding, agentic workspace, and engineering-design domains.

The agentic-workspace comparison makes the transfer-versus-fitting distinction particularly clear. RRSI reaches 90.5 on the Harvey LAB evolution split, lower than Meta-Harness at 93.0 and lower than the other principal evolved systems in several cases. Yet it obtains the strongest held-out performance:

Method Harvey LAB evolution Harvey LAB held-out OOD average
π\pi4 89.4 86.9 39.7
Meta-Harness 93.0 89.2 39.7
AHE 90.7 88.7 39.2
TTHE 91.1 88.5 37.9
HarnessX 91.8 89.1 39.7
RRSI 90.5 89.2 43.6

RRSI therefore has the smallest evolution-set gain among the reported evolved harnesses in this comparison while achieving the highest OOD average. Relative to the average baseline, the paper reports an OOD advantage of up to 22.9%. The result supports the paper’s main thesis: maximizing the evolution-set score is not an adequate proxy for learning a transferable harness mechanism.

The transfer result is not confined to judge-mediated evaluation. Harvey LAB, JobBench, and GDPval use LLM-based grading, creating a possible concern that RRSI might optimize for judge preferences. EngDesign and Frontier-Eng address this concern through deterministic simulators or testbenches. RRSI improves EngDesign during evolution and Frontier-Eng out of distribution, indicating that the observed transfer is not solely attributable to stylistic adaptation to an LLM judge.

Ablation and efficiency analysis

The ablation study separates proposal-side and acceptance-side regularization. Removing either group increases the evolution-set score but reduces OOD performance.

Variant Harvey LAB evolution ID held-out OOD average Tokens per trial
π\pi5 89.4 86.9 39.7 1.56M
Unregularized evolution 92.8 88.9 40.3 3.80M
Without proposal regularizers 90.7 88.8 41.9 2.69M
Without acceptance regularizers 91.5 88.7 41.0 3.59M
RRSI 90.5 89.2 43.6 2.42M

Removing proposal regularization reduces OOD performance from 43.6 to 41.9, despite changing the evolution score by only 0.2 points. This indicates that controlling where the search looks matters independently of the final acceptance criterion. Removing acceptance regularization increases the evolution score by one point but reduces OOD performance by 2.6 points and raises token cost by approximately 48% relative to RRSI. Removing both groups produces the highest evolution score, 92.8, but leaves the OOD average at 40.3, close to the unevolved harness.

The implication is direct: the proposal and selection mechanisms address different failure modes. Proposal regularization limits adaptive search concentration and improves exploration; selection regularization prevents noisy, leaking, or computationally excessive candidates from becoming permanent state. Neither mechanism is reducible to the other.

RRSI also reduces the cost of the final harness relative to all evolved baselines. It uses 2.42 million policy tokens per trial in the agentic-workspace analysis, compared with 3.80 million for unregularized evolution. AHE uses 3.82 million tokens per trial, 58% more than RRSI, while obtaining an OOD average 4.4 points lower.

Figure 4

Figure 4: RRSI dominates the other evolved harnesses in the reported cost–OOD-performance comparison, although the unevolved harness remains cheaper.

RRSI does not achieve the absolute minimum cost: π\pi6 uses 1.56 million tokens per trial. Thus the method’s efficiency result is relative to harnesses that evolve and improve. Its regularizers constrain the computational price of improvement rather than eliminating the cost of adaptation. The final harness also averages 26.3 steps per trial, compared with 27.3–34.6 for prior evolved harnesses, while π\pi7 averages 21.2 steps.

Policy and backbone transfer

The paper evaluates whether RRSI depends on the backbone used during evolution. In coding, independent evolution runs with Claude Opus 4.8 and Gemini 3.5 Flash both yield transfer to SWE-bench Verified. With Claude Opus 4.8, Terminal-Bench performance increases from 74.2 to 80.2 and SWE-bench performance from 82.0 to 83.8. With Gemini 3.5 Flash, Terminal-Bench improves from 64.6 to 78.7, a 14.1-point gain, while SWE-bench improves from 76.8 to 79.0.

The paper also evaluates the harness evolved with Gemini 3.5 Flash using the unseen, weaker Gemini 3.1 Flash Lite. Terminal-Bench performance rises from 11.2 to 14.6, a 3.4-point absolute gain and a 30.4% relative improvement. This result supports the claim that at least some learned mechanisms are not specific to the policy used during search. The absolute gain is nevertheless substantially smaller than that obtained with the search policy, and the low base performance of Gemini 3.1 Flash Lite makes the relative percentage sensitive to the denominator.

The cross-policy evidence is encouraging but bounded. It covers two policy families in the main coding comparison and one additional unseen policy in cross-model evaluation. It does not establish policy independence across arbitrary model architectures, context windows, tool APIs, or capability regimes.

Interpretation of the regularization perspective

The paper’s conceptual contribution is to characterize harness evolution as adaptive data analysis over executable agent systems. Every round reuses the evolution set, but the proposal distribution is itself conditioned on earlier measurements. Standard greedy selection therefore compounds multiple sources of selection bias:

  • Benchmark-specific fitting: candidate diffs can encode properties of the evolution tasks or their expected outputs.
  • Noise chasing: repeated stochastic evaluations can promote candidates that are transient winners.
  • Complexity accumulation: additional prompts, tools, memory, or control-flow branches can raise the evolution score while increasing inference cost without improving the underlying mechanism.
  • Search collapse: the proposer can repeatedly explore a familiar component family and neglect structural alternatives.

RRSI’s response is not to define a narrower class of harnesses. Instead, it regulates adaptive capacity per round, records evidence over the entire run, forces exploration under stagnation, screens leakage before scoring, imposes stability floors, links cost increases to measured gains, and prunes components lacking evidence of utility.

The analogies to π\pi8, π\pi9, and HH0 regularization are useful organizationally but should not be interpreted as a formal reduction to norm-regularized optimization. The edits are heterogeneous, discrete, and dynamically generated; the harness does not have a fixed continuous parameterization. The paper explicitly acknowledges this distinction. RRSI is best understood as a collection of procedural regularizers for a sequential program-search process.

Limitations and open questions

The evaluation holds backbone weights fixed, so it does not establish whether the same regularization principles remain effective when harness evolution is coupled to model-weight updates or post-training. The approach also depends on a finite evolution set, an empirical noise estimate, and several hyperparameters governing edit budgets, pruning windows, exploration, and cost acceptance. Although these are selected without consulting held-out or OOD benchmarks, their robustness across evolution budgets and task scales is not fully established.

The leakage critic is itself an LLM-based component, and its ability to identify subtle benchmark-specific behavior is not quantified independently. A candidate can avoid explicit task names or values while still exploiting distributional regularities in the evolution set. Similarly, the attribution of bundled edits remains imperfect in early rounds, because all edits in a candidate inherit the same measured score and cost change. The annealed budget improves attribution later but does not provide causal identification of individual edits.

The experiments cover multiple domains, verifiers, and policies, but the evidence remains limited to the reported harness architectures and evolution procedures. EngDesign lacks an in-distribution held-out split because of its size, and the engineering evaluation contains a domain relationship between EngDesign and Frontier-Eng that is not completely independent. The paper therefore leaves open how RRSI behaves under substantially longer evolution horizons, larger candidate populations, continual task streams, different proposer policies, and architectures whose harnesses are not naturally represented as editable source components.

Conclusion

RRSI frames recursive harness evolution as an adaptive optimization problem whose principal risk is not lack of evolution-set improvement but failure to transfer that improvement. Its proposal-side and selection-side regularizers reduce benchmark-specific fitting, noise chasing, structural accumulation, and unnecessary inference cost while preserving an open harness edit space. Across coding, agentic workspace, and engineering-design tasks, RRSI sacrifices some evolution-set score in exchange for stronger held-out performance, achieving up to 14.1 points of in-distribution improvement, up to 4.7 points out of distribution, and substantially lower policy-token cost than unregularized evolution. The central empirical conclusion is that persistent harness improvement depends on regulating how feedback changes the search trajectory, not merely on expanding the set of editable agent components.

Paper to Video (Beta)

No one has generated a video about this paper yet.

Whiteboard

Explain it Like I'm 14

1. What is this paper about?

This paper introduces a method called RRSI, short for Regularized Recursive Self-Improvement of Agent Harnesses.

The main idea is that an AI agent is not just the LLM itself. It also has a surrounding system, called a harness, that tells it:

  • what instructions to follow,
  • which tools to use,
  • how to plan and act,
  • what information to remember,
  • how to handle mistakes, and
  • what information to keep in its working memory.

For example, the same LLM might perform much better if it is given a better system for reading files, using a computer terminal, checking its work, and recovering from errors.

Researchers have begun using AI to automatically improve these harnesses. However, this can create a problem: the AI may learn tricks that work only on the particular test questions it has seen. This is called overfitting.

RRSI is designed to help the agent learn useful improvements that also work on new and different tasks.

2. What questions does the research ask?

The paper focuses on several important questions:

  1. Can an AI improve the instructions and tools surrounding another AI?
  2. Do automatically improved harnesses work on new tasks, or only on the tasks used during improvement?
  3. Can the improvement process avoid memorizing specific answers or test cases?
  4. Can the improved agent become more capable without using much more computing power?
  5. Which parts of RRSI are most important?

The researchers are especially interested in the difference between:

  • evolve-set performance: how well the agent performs on tasks used to improve it, and
  • held-out performance: how well it performs on new tasks that it never saw during improvement.

This is similar to studying for a test. A student who memorizes the exact practice questions may score highly on those questions but perform poorly on a new test. A student who learns the underlying ideas should do well on both.

3. How did the researchers conduct the study?

The basic improvement process

The researchers begin with a LLM whose internal settings, or weights, remain unchanged. They modify only its harness.

The process works roughly like this:

  1. The current harness tries to solve a group of tasks.
  2. Researchers record what went well and what went wrong.
  3. Another LLM suggests changes to the harness.
  4. The suggested versions are tested.
  5. A promising version becomes the new harness.
  6. The process repeats.

This is called recursive self-improvement because feedback from the current agent is used to create a better version of the system surrounding it.

Why ordinary improvement can fail

If the same tasks are used again and again, the system may begin to memorize details about them. It might also keep changes that appear helpful only because of random luck.

For instance, imagine changing a robot’s instructions after watching it play the same ten games repeatedly. The robot might learn a trick that works in those ten games but fails in every new game.

What RRSI changes

RRSI adds safeguards, or regularization, to make the improvement process more careful. The main safeguards are:

Smaller and more controlled updates

Early in the process, the system may try several related changes at once. Later, it is allowed to make fewer changes at a time.

This makes it easier to identify which change helped. It is like changing one part of a bicycle at a time so you know which repair fixed the problem.

Remembering past experiments

RRSI keeps a record of:

  • which part of the harness was changed,
  • what idea the change was testing,
  • whether it helped,
  • whether it increased the amount of computer work, and
  • whether the change was accepted or rejected.

This prevents the system from repeatedly trying ideas that already failed.

Exploring neglected possibilities

If the system keeps changing only prompts, RRSI may encourage it to examine other parts of the harness, such as memory, tools, or the order of actions.

This is similar to making sure a student studies several topics instead of practicing only one favorite chapter.

Rejecting test-specific tricks

A separate checking system, called a critic, looks for changes that directly include:

  • task names,
  • exact answers,
  • special values from the test set, or
  • other information that would work only on the training tasks.

Such changes are rejected before they can influence the results.

Ignoring improvements caused by random noise

AI systems can behave differently each time they attempt the same task. Because of this, a candidate harness might appear better simply by chance.

RRSI measures this natural variation and requires a new version to improve by more than the expected random fluctuation.

Controlling computing cost

A new harness is not accepted just because it gets a slightly higher score. If it uses many more tokens, or requires much longer reasoning, the extra cost must be justified by a meaningful improvement.

A token is a small piece of text processed by the LLM. More tokens usually mean more time and money.

Removing unhelpful parts

RRSI tracks which components of the harness are useful. Components that repeatedly fail to help can be removed.

The goal is not simply to make the harness more powerful, but also to keep it reasonably simple and efficient.

The benchmarks

The researchers tested RRSI in three broad areas:

  • Coding, including terminal tasks and fixing software bugs.
  • Workspace tasks, such as legal and professional work.
  • Engineering design, where proposed designs are checked by simulations or testing programs.

They used eight benchmarks in total. In each area, the harness was improved using one set of tasks and then tested on different tasks it had not seen.

The researchers compared RRSI with:

  • the original, unimproved harness, and
  • four other automatic harness-improvement methods.

4. What did the researchers find?

RRSI improved performance on new tasks

The most important finding is that RRSI improved performance not only on the tasks used for improvement, but also on unseen tasks.

Across the experiments:

  • RRSI improved the evolution benchmark by as much as 14.1 percentage points.
  • It improved out-of-distribution benchmarks by as much as 4.7 percentage points.
  • It improved every held-out test set in the main experiments.
  • It used about 30% fewer policy tokens than unregularized evolution.

“Out-of-distribution” means tasks that are meaningfully different from the tasks used during improvement, such as a different type of work or a different tool system.

Ordinary methods often overfit

The other improvement methods often achieved high scores on the tasks they evolved against. However, their gains were much smaller on new benchmarks.

In some cases, they performed no better than the original harness. One method even performed worse than the starting harness on the average of the new tasks.

This supports the paper’s central claim: simply choosing the highest-scoring version on the improvement tasks is not enough.

Regularization improved generalization

The experiments removed different parts of RRSI to see what happened.

When the researchers removed the proposal safeguards or the selection safeguards:

  • performance on the improvement tasks often increased,
  • performance on new tasks decreased, and
  • computing costs increased.

This is important because it shows that a higher score on the original tasks can actually be misleading. The safeguards may produce a slightly smaller improvement on familiar tasks, but they produce a more useful and reliable system overall.

The improvements worked with different models

The researchers evolved harnesses using different LLMs, including Claude and Gemini. The improvements transferred to other models as well.

For example, a harness improved using one Gemini model also helped a smaller Gemini model that had not been involved in the improvement process.

This suggests that RRSI may discover general strategies, such as better planning or error recovery, rather than tricks tied to one specific model.

The system became more efficient

RRSI produced an improved harness that used fewer tokens than the other evolved harnesses.

This matters because an agent that solves tasks correctly but uses an enormous amount of computation may be too expensive to use in practice.

5. Why are these results important?

The paper shows that improving an AI agent is not only about making it score higher on the tasks it has already seen. The real goal is to create improvements that continue to work in new situations.

RRSI treats automatic agent improvement more like careful scientific experimentation:

  • change a limited number of things,
  • record what happened,
  • avoid repeating failed ideas,
  • reject cheating or test-specific tricks,
  • account for random variation, and
  • remove changes that are not worth their cost.

The research suggests that AI systems can improve their own surrounding instructions and tools, but this process needs controls. Without them, the system may become better at “studying the test” rather than becoming genuinely better at solving problems.

Conclusion and potential impact

RRSI could help developers build stronger AI agents without retraining the underlying LLM. Instead of changing the model’s internal knowledge, developers can improve the system around it: its prompts, tools, memory, planning process, and error recovery.

If the results hold up in future studies, this approach could lead to AI agents that:

  • solve a wider range of tasks,
  • transfer their skills to unfamiliar situations,
  • use less computing power,
  • avoid memorizing benchmark-specific tricks, and
  • improve more safely and reliably over time.

However, the paper also has limitations. The LLM itself was kept fixed, and the method still depends on the quality of the tasks and feedback used during improvement. More research is needed to see whether RRSI works with other models, tools, agent designs, and longer-running improvement processes.

Knowledge Gaps

Knowledge Gaps, Limitations, and Open Questions

  • Statistical reliability is not established: The paper reports point estimates but does not provide confidence intervals, significance tests, variance across independent evolution seeds, or task-level uncertainty, making it unclear whether the reported transfer gains are robust.
  • The number of evolution runs is unclear: It is not specified whether results represent single runs or averages over multiple independent proposer, evaluator, and trajectory-sampling runs.
  • The regularization hyperparameters may be overfit: Parameters such as the noise band δ\delta, pruning window, exploration window, edit budgets, and cost coefficients (β0,β1)(\beta_0,\beta_1) are selected using the evolve set, but the paper does not quantify their sensitivity or assess whether this creates another layer of adaptive overfitting.
  • The relative contribution of individual regularizers remains unresolved: The ablations remove proposal-side or acceptance-side groups as a whole, without separately isolating annealed sparsity, credit assignment, structured exploration, leakage screening, stability-aware acceptance, cost-aware acceptance, and pruning.
  • The effectiveness of the leakage critic is not independently validated: The paper does not report false-positive and false-negative rates, inter-rater agreement with human reviewers, or experiments showing how performance changes when the critic is imperfect or adversarially bypassed.
  • Leakage detection is limited to explicit task-specific content: The method may not detect indirect memorization, benchmark-specific strategies encoded through generic-looking prompts, latent correlations, or edits that exploit verifier artifacts without naming task-specific entities.
  • The method lacks a formal generalization guarantee: The paper motivates RRSI using adaptive data analysis, but it does not derive bounds relating evolve-set reuse, candidate count, search rounds, evaluation noise, and out-of-distribution performance.
  • The definition of “generalization” is narrow: Transfer is evaluated across selected benchmarks and task formats, but the study does not test substantially different domains, languages, modalities, interaction protocols, tool APIs, or open-ended real-world task streams.
  • Benchmark diversity may still be insufficient: Several agentic workspace benchmarks share similar task structures and judge-mediated evaluation, so the observed transfer may partly reflect common task or verifier conventions rather than reusable harness mechanisms.
  • The claimed cross-policy robustness is sparsely tested: Cross-policy experiments use only a small number of models and primarily focus on coding tasks; robustness across substantially different model families, capability levels, context windows, instruction-following behaviors, and proprietary/open-weight models remains unknown.
  • Weight-updating recursive self-improvement is not studied: The conclusions may not extend to settings where the backbone is fine-tuned, distilled, reinforced, or otherwise updated alongside the harness.
  • Long-horizon recursive evolution is unexplored: Experiments use a fixed and apparently short evolution schedule, leaving open whether regularization prevents complexity accumulation, collapse, or drift over hundreds or thousands of rounds.
  • Performance under nonstationary task streams is unknown: The method is evaluated with a fixed evolve set and fixed benchmark distributions, not with changing tasks, tools, policies, or environments that require continual adaptation.
  • The cost analysis is incomplete: The paper measures policy tokens consumed by the final harness but does not report the total computational and monetary cost of proposing, critiquing, evaluating, and evolving candidates.
  • The cost–performance trade-off is not fully characterized: It remains unclear how performance changes as candidate count, number of trials per task, evolution rounds, and evaluation budget vary, or whether comparable transfer can be obtained more cheaply through additional evaluation rather than regularization.
  • The noise estimate may be unreliable for heterogeneous tasks: The procedure for estimating δ\delta from repeated base-harness evaluations may not capture task-dependent variance, heavy-tailed outcomes, correlations across candidates, or changes in variance caused by later harness edits.
  • Selection remains based primarily on a single empirical score: The method does not examine more statistically principled alternatives such as confidence-bound selection, cross-validation over evolve tasks, held-out validation during evolution, or multi-objective optimization over score, cost, and robustness.
  • The effect of task-level resampling is not investigated: It is unclear whether using fresh evolution tasks, rotating validation subsets, or task-level cross-validation would reduce overfitting more effectively than the proposed history-based constraints.
  • The quality of credit assignment is uncertain: Candidate edits can modify multiple interacting harness components, so recording a source diff and score change may not identify causal contributions or distinguish synergistic mechanisms from incidental correlations.
  • Pruning may remove delayed-benefit components: The paper does not evaluate whether the fixed pruning window incorrectly deletes mechanisms whose value appears only on rare, difficult, or long-horizon tasks.
  • The open edit space creates unresolved safety and reliability risks: The study does not assess whether evolution can introduce insecure tool permissions, destructive control flow, privacy violations, prompt-injection vulnerabilities, or behavior that is beneficial on benchmarks but unsafe in deployment.
  • Verifier gaming is not comprehensively examined: Deterministic simulators and unit tests reduce judge variance but may still contain exploitable shortcuts; the paper does not test whether evolved harnesses exploit weaknesses in any verifier.
  • Human usefulness and output quality are not directly evaluated: Improvements in benchmark scores are not supplemented with human judgments of correctness, usefulness, readability, safety, or maintainability of the resulting deliverables and harness code.
  • Harness maintainability is unmeasured: The paper claims that RRSI favors reusable mechanisms, but it does not assess code complexity, interpretability, debuggability, portability, or the engineering effort required to understand and maintain evolved harnesses.
  • Baseline comparisons may not establish complete fairness: Although the methods share an initial harness, policy, evolve set, and candidate budget, the paper does not fully compare total inference budgets, proposer prompts, number of evaluations, implementation maturity, or hyperparameter-selection procedures across methods.
  • The relationship between evolve-set gains and transfer is not modeled: The experiments show an empirical trade-off but do not determine whether lower evolve-set improvement is intrinsically beneficial, merely correlated with simpler edits, or dependent on the particular benchmark and score scale.
  • Ceiling and floor effects are insufficiently addressed: Some benchmarks have high base performance while others have very low performance for weaker models, making absolute and relative gains difficult to compare and potentially masking failures or regressions.
  • Reproducibility details remain incomplete: Important implementation choices—such as exact proposer and analyst prompts, candidate-generation constraints, edit parsing, trial allocation, stopping rules, and the full hyperparameter-selection process—are not presented in the paper text sufficiently to independently reproduce the results.
  • The paper does not test adversarial or distribution-shifted evaluation: Future work is needed to determine whether RRSI remains effective when held-out tasks are deliberately designed to expose benchmark-specific assumptions or to stress tool, context, and recovery behavior.
  • The persistence of learned mechanisms is unknown: It remains unresolved whether evolved harness improvements continue to transfer after tool versions, backbone models, task instructions, context limits, or verifier implementations change.
  • The optimal regularization schedule is unexplored: The cosine annealing rule is selected a priori, but alternative schedules, adaptive budgets, and schedules conditioned on uncertainty or observed progress are not compared.
  • Interactions between harness components are not systematically analyzed: Because prompts, memory, tools, control flow, and context management can be highly coupled, it is unclear which classes of edits account for transfer and whether some combinations are necessary or harmful across domains.

Practical Applications

Immediate Applications

  • Production agent-harness optimization for software engineering
    • Sector: Software development, DevOps, cloud platforms.
    • Organizations can apply RRSI to improve coding-agent harnesses without retraining the underlying LLM. The system can iteratively revise prompts, repository-navigation logic, terminal-tool descriptions, error-recovery routines, context compaction, and planning/verification workflows.
    • Potential tools and workflows: An internal “harness optimizer” that evaluates candidate configurations on historical bug-fixing tasks, rejects benchmark-specific edits, and deploys only changes that improve performance without excessive token use.
    • Evidence from the paper: RRSI improved Terminal-Bench performance by up to 14.1 points in one policy setting and transferred gains to SWE-bench Verified, including when evaluated with a different model.
    • Assumptions and dependencies: Reliable automated tests or verifiers must be available; repository data must be properly isolated from evolution tasks; production deployment requires sandboxing, code-review gates, rollback, and protection against prompt or tool-interface changes that could introduce security vulnerabilities.
  • Cost-aware optimization of enterprise LLM agents
    • Sector: Customer support, operations, consulting, knowledge management, and cloud AI.
    • RRSI can be used to reduce unnecessary planning loops, redundant tool calls, oversized prompts, and excessive memory retrieval while preserving task quality. Its complexity-aware acceptance rule provides a practical mechanism for rejecting changes whose token cost is not justified by performance gains.
    • Potential product: A monitoring dashboard showing task success, token consumption, trajectory length, rejected edits, and transfer performance across customer or operational workloads.
    • Evidence from the paper: The final RRSI harness used approximately 30% fewer policy tokens than unregularized evolution and was cheaper than the other evolved harnesses tested.
    • Assumptions and dependencies: Token count is only a proxy for total cost; latency, tool charges, human-review time, and infrastructure usage should also be measured. Cost reductions must not remove safety checks or important verification steps.
  • Robust agent configuration for legal and professional-workspace tasks
    • Sector: Legal technology, finance, consulting, human resources, and document-intensive enterprise work.
    • Firms can evolve workflows for document retrieval, source citation, multi-step analysis, drafting, self-review, and context management using representative but held-out work items. The leakage critic is particularly useful for preventing the system from embedding client names, answers, or task-specific patterns into the harness.
    • Potential workflow: Use anonymized historical matters for evolution, reserve unseen matters for evaluation, and require human approval before changes are released to production.
    • Evidence from the paper: RRSI improved held-out and out-of-distribution agentic-workspace benchmarks, including legal and economically valuable task settings.
    • Assumptions and dependencies: Evaluation must reflect substantive correctness rather than merely stylistic preferences of an LLM judge. Confidentiality, privilege, data residency, and auditability requirements may restrict the feedback data available to the optimizer.
  • Engineering-design and simulation-agent workflows
    • Sector: Engineering, robotics, manufacturing, architecture, and industrial R&D.
    • RRSI can improve agents that iteratively generate designs, run simulations, inspect failures, modify parameters or code, and submit a final design. The approach is especially suitable where deterministic simulators or testbenches provide objective feedback.
    • Potential tools: An engineering-agent harness that automatically improves task decomposition, simulation orchestration, constraint checking, failure recovery, and result reporting.
    • Evidence from the paper: Improvements transferred from EngDesign to Frontier-Eng, where deterministic simulation or testbench grading reduced the risk that gains were caused only by judge-model preferences.
    • Assumptions and dependencies: Simulators must adequately represent real-world constraints. Deployment in physical systems still requires safety certification, domain-expert review, hardware testing, and tolerance for simulation-to-reality gaps.
  • Evaluation and quality-assurance infrastructure for agent developers
    • Sector: AI research, model evaluation, platform engineering, and MLOps.
    • RRSI provides a practical template for evaluating whether an agent improvement is genuinely reusable rather than overfit to a development benchmark. Teams can incorporate:
    • separate evolution, in-distribution holdout, and out-of-distribution evaluation sets;
    • baseline noise estimation;
    • candidate-diff leakage screening;
    • edit-history and attribution logs;
    • token and trajectory-cost reporting; and
    • conservative acceptance thresholds.
    • Potential product: A continuous-integration system for agent harnesses that treats prompts, tools, memory policies, and control-flow code as versioned artifacts.
    • Assumptions and dependencies: Held-out tasks must remain inaccessible during evolution, and evaluation sets must be sufficiently diverse. LLM-based critics and judges can themselves be noisy or biased, so deterministic tests and human audits remain important.
  • Academic research on modular agent design
    • Sector: Academia and open-source agent research.
    • Researchers can use RRSI to study which harness mechanisms transfer across tasks, models, and tool ecosystems. The logged history of proposed, rejected, accepted, and pruned edits can support causal or ablation-style analysis of prompts, memory, tools, planning, and context management.
    • Potential research workflow: Publish a base harness, evolution set, untouched transfer suites, complete edit histories, evaluation seeds, and cost measurements rather than reporting only the best score on the evolution benchmark.
    • Assumptions and dependencies: Reproducibility depends on access to the same backbone models, tool environments, benchmark versions, and evaluator configurations. Results should not be generalized beyond the tested domains without additional validation.
  • Policy and governance standards for self-improving agents
    • Sector: AI governance, standards bodies, regulators, and enterprise risk management.
    • RRSI supports concrete governance requirements for systems that modify their own prompts, tools, memory, or control flow:
    • maintain immutable evaluation sets;
    • require change logs and provenance;
    • screen for benchmark or user-data leakage;
    • impose resource budgets;
    • validate changes on independent tasks;
    • preserve rollback versions; and
    • prohibit autonomous deployment of unreviewed harness changes in high-risk domains.
    • Potential policy artifact: A “harness change-management” standard analogous to software supply-chain or model-risk-management controls.
    • Assumptions and dependencies: Organizations must be able to inspect harness source and evaluation traces. These controls are less effective when agents can modify opaque external services or when the verifier is easily manipulated.
  • Personal productivity and daily-life assistants
    • Sector: Consumer software and personal knowledge management.
    • A local or hosted assistant could improve how it organizes files, summarizes information, schedules tasks, uses productivity tools, and recovers from failed actions. RRSI’s pruning and cost controls could prevent the assistant from accumulating unnecessary memory, lengthy prompts, or redundant action loops.
    • Potential workflow: Optimize on synthetic or user-approved tasks, evaluate on separate tasks, and ask for explicit consent before changing access permissions or automation behavior.
    • Assumptions and dependencies: Personal data must not be used as unrestricted training or evolution feedback. Strong permission boundaries, transparency about changes, and easy rollback are essential.

Long-Term Applications

  • Continual self-improvement of deployed agents
    • Sector: Autonomous software, enterprise automation, robotics, and long-running digital services.
    • RRSI could become part of an online adaptation loop in which agents learn from operational failures while retaining only changes that transfer across time periods, users, and environments. The evolution history could distinguish broadly useful mechanisms from temporary workload-specific adaptations.
    • Potential system: A versioned agent controller with shadow evaluation, canary deployment, rollback, and automatic retirement of unproductive components.
    • Dependencies and risks: The paper evaluates finite, offline evolution sets rather than unrestricted online learning. Continual deployment requires protection against feedback loops, distribution shift, adversarial users, privacy leakage, and irreversible behavioral drift.
  • Cross-model and cross-provider harness portability
    • Sector: AI infrastructure and model marketplaces.
    • Because the paper reports transfer to policies that were not used during evolution, future systems could maintain model-agnostic harness layers for planning, tool use, memory, and verification. This could allow organizations to switch between providers or model sizes without rebuilding the entire agent architecture.
    • Potential product: A compatibility and benchmarking layer that tests one harness across multiple models and automatically removes model-specific assumptions.
    • Dependencies: Transfer is not guaranteed across radically different context limits, tool APIs, instruction-following behavior, or multimodal capabilities. Harnesses may need model-specific adapters, and portability must be measured rather than assumed.
  • Autonomous robotics and embodied systems
    • Sector: Robotics, logistics, industrial automation, and autonomous vehicles.
    • RRSI could optimize high-level robot behaviors such as task decomposition, sensor-query policies, recovery from failed actions, memory of workspace state, and coordination with external tools or simulators.
    • Potential workflow: Evolve in simulation, test on unseen simulated environments, then conduct restricted physical trials with safety monitors and human override.
    • Dependencies and risks: The current evidence concerns software agents and engineering simulations, not physical robots. Real-world deployment requires handling sensor noise, hardware wear, real-time constraints, safety-critical failures, and sim-to-real transfer.
  • Healthcare decision-support and clinical workflow agents
    • Sector: Healthcare and biomedical research.
    • A carefully constrained version could optimize administrative and decision-support workflows: retrieving patient information, checking documentation completeness, preparing summaries, coordinating referrals, or proposing questions for clinician review. RRSI could help reduce redundant context and enforce verification steps.
    • Potential tool: A clinician-supervised harness optimizer evaluated on de-identified, institution-specific cases and independent external cases.
    • Dependencies and risks: The paper does not establish clinical safety or diagnostic validity. Use would require privacy protection, prospective validation, calibrated uncertainty, clinician oversight, regulatory approval where applicable, and strict exclusion of autonomous high-stakes decisions.
  • Education and adaptive tutoring systems
    • Sector: Education and learning technology.
    • RRSI could optimize tutoring-agent strategies for explanation, questioning, misconception diagnosis, pacing, tool use, and feedback. Independent evaluation sets could test whether improvements generalize across subjects, age groups, curricula, and student backgrounds.
    • Potential product: A tutor harness that adapts instructional workflows while preserving pedagogical constraints and limiting unnecessary interaction length.
    • Dependencies and risks: Benchmark scores may not capture genuine learning. Longitudinal studies, teacher review, fairness analysis, child-safety controls, and measures of durable learning—not merely answer accuracy—would be required.
  • Safety-oriented agent architecture search
    • Sector: AI safety, cybersecurity, and high-assurance software.
    • The proposal and selection mechanisms could be extended so that candidate harnesses are judged not only on task success and token cost but also on robustness, policy compliance, resistance to prompt injection, least-privilege tool use, and recoverability.
    • Potential research direction: Multi-objective RRSI with hard safety gates, adversarial evaluation, formal checks for selected control-flow properties, and independent red-team suites.
    • Dependencies: The current method screens explicit leakage and manages complexity but does not provide comprehensive security guarantees. Safety objectives must be measurable, independently evaluated, and protected from optimization-induced gaming.
  • Federated or organization-specific harness evolution
    • Sector: Finance, government, healthcare, and privacy-sensitive enterprise systems.
    • Multiple organizations could evolve compatible harnesses using local task feedback while sharing abstract edit metadata, reusable mechanisms, or anonymized performance statistics rather than raw data.
    • Potential workflow: Federated evaluation of candidate harness components, followed by local acceptance based on privacy, cost, and domain-specific performance.
    • Dependencies: Privacy-preserving aggregation, comparable verifiers, protection against poisoned feedback, and governance over shared harness components would be necessary. Local improvements may not transfer when workflows, laws, or tool ecosystems differ substantially.
  • Automated creation of agent platforms and tool ecosystems
    • Sector: Software platforms, cloud services, and enterprise automation.
    • Over time, RRSI could evolve not only prompts and control flow but also tool descriptions, memory schemas, subagent roles, context policies, and orchestration graphs. This may produce domain-specific agent platforms for coding, research, design, or operations.
    • Potential product: A “harness compiler” that converts task requirements and evaluation interfaces into a tested, versioned agent workflow.
    • Dependencies and risks: The larger the editable system, the harder it becomes to attribute improvements and detect emergent failure modes. Longer evolution runs, richer causal attribution, stronger sandboxing, and human approval would be needed before allowing autonomous architectural changes.
  • Regulated benchmarking and certification of self-improving agents
    • Sector: Public policy, procurement, finance, healthcare, and safety-critical industries.
    • The distinction between evolution-set performance and transfer performance could support certification regimes requiring an agent to demonstrate improvement on unseen, adversarial, cross-domain, and cost-constrained evaluations before deployment.
    • Potential standard: Certification reports could include the initial and final harnesses, all accepted edits, evaluator independence, resource changes, leakage checks, and performance confidence intervals.
    • Dependencies: Agreement is needed on benchmark governance, evaluator independence, update-trigger thresholds, and how frequently a deployed agent must be recertified. Certification cannot rely solely on the same benchmark used to optimize the system.

Glossary

  • Adaptive empirical optimization: Optimization in which future search decisions depend on measurements previously collected from the same data or tasks. “Harness evolution can therefore be viewed as adaptive empirical optimization over an unusually expressive search space.”
  • Adaptive overfitting: Overfitting caused by repeatedly adapting a system to feedback from a reused evaluation set. “...creating an adaptive overfitting risk: evolve-set performance may improve without corresponding gains on unseen tasks.”
  • Agent harness: The collection of prompts, control logic, tools, memory, and context-management mechanisms surrounding a model. “A frozen backbone model is wrapped in a harness of prompts, control flow, tool interfaces, memory and context management.”
  • Agentic workspace: An environment in which an agent performs open-ended, tool-mediated work rather than a narrowly defined prediction task. “Across eight benchmarks spanning coding, agentic workspace and engineering design tasks...”
  • Annealed update sparsity: A schedule that gradually reduces the number of modifications permitted in each update. “L0L_0-Style Annealed Update Sparsity.”
  • Backbone policy: The underlying model whose behavior is shaped by the surrounding harness. “We consider an agent A=(π,H)A = (\pi, H) built from a backbone policy π\pi and a harness HH.”
  • Cardinality constraint: A restriction on the number of active elements, such as the number of edits in an update. “The edit budget is the closest to an L0L_0-style cardinality constraint...”
  • Candidate harness: A proposed modified version of the current agent harness. “The candidates are evaluated on the same evolve set; and the best candidate is selected as the next incumbent.”
  • Context management: The process of controlling which information is presented to the model at each step. “...the memory and context management that decides what the policy sees at each step.”
  • Credit assignment: Determining which change or mechanism caused an observed outcome. “As later rounds allow fewer edits per candidate, it becomes easier to identify which change is responsible for an observed improvement.”
  • Critic: A component that inspects proposed changes for undesirable or benchmark-specific content. “The selector is equipped with a critic and a pruner...”
  • Cross-round failure feedback: Feedback summarizing failures across multiple optimization rounds. “The proposer, the analyst that writes the cross-round failure feedback and the leakage critic are all Claude Opus 4.8.”
  • Empirical noise band: An estimated range representing score variation attributable to stochastic evaluation noise. “We treat the search as stalled when its progress over the previous ww rounds remains within the empirical noise band δ\delta.”
  • Empirical score: A performance estimate calculated from a finite set of observed trials. “S^\hat S is the empirical score obtained from a finite number of stochastic agent runs.”
  • Evidence-aware credit assignment: Credit assignment that incorporates the complete history of prior evaluations and outcomes. “RRSI therefore records, for every evaluated candidate, the component it modifies, the hypothesis it tests, the source diff, the resulting score and cost changes, and whether the candidate was accepted.”
  • Evolution set: The task set used to propose and evaluate harness modifications. “At round tt, the current harness HtH_t is executed on an evolve set Devolve\mathcal{D}_{\mathrm{evolve}} to obtain trajectories...”
  • Fitness signal: An empirical measurement used to guide the optimization of a system. “This inherits both the mechanisms and the risks of self-improving agents that search over their own code under an empirical fitness signal...”
  • Frozen backbone model: A model whose parameters remain unchanged during harness optimization. “Our study focuses on harness-level recursive self-improvement with frozen backbone models...”
  • Held-out benchmark: A benchmark withheld from the optimization process and used to measure generalization. “...the resulting harness is evaluated unchanged on both the evolve benchmark and SWE-bench Verified.”
  • Hypothesis space: The set of possible solutions or system configurations considered by an optimization procedure. “Instead of restricting this hypothesis space directly, we regularize the search trajectory through it.”
  • In-distribution: Drawn from the same general task distribution as the data used for optimization. “The in-distribution held-out split of Harvey LAB gains 2.3...”
  • Inference cost: The computational expenditure incurred while a model generates outputs. “Thus additional inference cost must be justified by measurable performance improvement.”
  • Lasso/L1L_1 regularization: A regularization method that encourages sparsity by penalizing the absolute magnitude of parameters or components. “This process imitates the Lasso/L1L_1-style sparsification...”
  • Leakage screening: Detection and removal of proposed changes that encode information specific to the evaluation tasks. “Before full evaluation, a critic reads each candidate diff and rejects edits that explicitly encode task names, entity names, task-specific values, answers, or other logic specific to the evolve benchmark...”
  • Noise-adjusted floor: A minimum acceptable score threshold that accounts for estimated evaluation noise. “A candidate must satisfy the noise-adjusted floor...”
  • Out-of-distribution (OOD): Evaluation on tasks or data differing substantially from those used during optimization. “RRSI improves every split outside the evolve set, in all three domains.”
  • Policy-token cost: The number of tokens generated by the underlying model during an agent trajectory. “We use policy-token cost as a common measurable proxy for this footprint.”
  • Pruner: A component that removes changes judged ineffective, excessively costly, or unnecessary. “The selector is equipped with a critic and a pruner: the critic screens benchmark-specific proposals, while the pruner, removes changes that are too small, too expensive, or no longer useful.”
  • Recursive self-improvement (RSI): Iterative improvement in which a system’s feedback is used to modify the system or its operating mechanism. “Such iterative harness evolution provides a practical form of recursive self-improvement (RSI) at the agent-system level...”
  • Regularization: The use of constraints or penalties to reduce overfitting and discourage unnecessarily complex solutions. “We introduce Regularized Recursive Self-Improvement of Agent Harnesses (RRSI), which incorporates the principles of regularizations into harness self-improvement...”
  • Reinforcement-style trajectory: A sequence of actions, observations, and intermediate states produced while an agent performs a task. “Given a task xx with its environment, the agent produces a trajectory τA(x)\tau \sim A(\cdot \mid x) and a deliverable...”
  • Ridge/L2L_2 regularization: A regularization method that discourages large parameter magnitudes or overall solution complexity. “This process is analogous to Ridge/L2L_2-style shrinkage...”
  • Search trajectory: The sequence of candidate configurations visited during an optimization process. “RRSI regularizes the search trajectory through it.”
  • Selection-side constraint: A restriction governing which proposed modifications may be retained. “On the selection side, we constrain which empirical improvements are strong enough, efficient enough, and sufficiently free of leakage to survive.”
  • Sparse update: An update that changes only a limited number of components. “Sparse updates limit how many mechanisms can change in response to one round of feedback...”
  • Structural pruning: Removing entire system components that have not demonstrated useful contributions. “Structural pruning is analogous to Lasso/L1L_1-style sparsification because persistently unproductive components are removed from the retained harness...”
  • Stochastic evaluation: Evaluation whose results vary because model execution or other parts of the process are probabilistic. “Repeatedly selecting among noisy evaluations can convert stochastic winners into permanent search state.”
  • Test-time computation: Computation performed while solving or evaluating tasks, rather than during model training. “...apparent improvements can arise from task-specific fitting or increased test-time computation rather than reusable mechanisms...”
  • Trajectory: The complete sequence of states, actions, and outputs generated during one agent run. “With kk trials per task, we use... r(x,τx(j))r(x,\tau_x^{(j)})...”
  • Transfer evaluation: Evaluation of a system on tasks or benchmarks different from those used for optimization. “We keep the same open edit space and instead regularize the search dynamics...”
  • Verifier: A mechanism that assesses whether an agent’s output satisfies task requirements. “The verifier can be a unit-test suite in coding environments or a LLM-as-a-judge program in agentic workspace environments.”

Open Problems

We found no open problems mentioned in this paper.

Tweets

Sign up for free to view the 15 tweets with 277 likes about this paper.