Trustworthy Recursive Self-Improvement in the Era of Large Models: Foundation, Risks, Evaluation and Open Challenges
Organizations: Gaoling School of Artificial Intelligence, Renmin University of China · University of Chinese Academy of Sciences
Abstract
AI systems built around large models increasingly use experience and feedback to make persistent changes to models, prompts, memories, tools, and workflows. Recursive self-improvement (RSI) extends this process to inductive biases and to the mechanisms that govern future updates, which can themselves be revised and reused across improvement cycles. Yet self-modification alone does not guarantee trustworthy improvement. Reported gains may reflect flawed evaluations, previously acquired capabilities may deteriorate, and compliance with behavioral constraints may weaken. Compromised artifacts or sensitive information may also persist in successor systems. Changes to improvement mechanisms may invalidate earlier verification results and make human oversight less effective. This survey presents an operational definition and process framework for RSI and organizes the requirements for trustworthy RSI into four interconnected themes: genuine and sustained improvement; behavioral constraints, alignment, and fairness; system security and privacy; and transparency and controllability. We examine these themes from three perspectives: Improvement Validity, Constraint Preservation, and Effective Oversight. This analysis covers improvement diagnosis, proposal generation, proposal evaluation, and update implementation (S1--S4), including the recursive application of these stages to improvement mechanisms (RI). We review risks, safeguards, and evaluation evidence for individual updates, effects inherited by successor systems, and revisions to improvement mechanisms, while distinguishing direct RSI findings from evidence in related systems. Finally, we examine evaluation settings, identify requirements for independent and longitudinal assessment, and discuss applications and open research problems.
Figures & tables
| Survey | Main analytical focus | MT | IL | MR | LA | JE |
| Trustworthiness-oriented surveys | ||||||
| Li et al. (2023) | Trustworthiness principles and practices for AI | — | — | — | ||
| Liu et al. (2023) | Trustworthiness requirements and methods for LLMs | — | — | — | ||
| Yu et al. (2025) | Trustworthiness of LLM agents | — | — | — | ||
| Qi et al. (2026) | Trustworthiness of agentic workflows | — | ||||
| Self-evolution and RSI-oriented surveys | ||||||
| Approach | Who determines the inductive bias ? | Is revised autonomously? | Is the bias update function revised and reused? |
| Conventional machine learning | Human designer | ✗ | ✗ |
| Reinforcement learning | Human designer | ✗ | ✗ (learning rule fixed) |
| Meta-learning | Meta-learner | ✓ | ✗ (meta-update rule fixed) |
| AutoML | Automated search | ✓ | ✗ (search rule fixed) |
| RSI | Bias update function | ✓ | ✓ (the revised guides later bias updates) |
| Analytical role | Theme | Requirement groups | RSI-specific question |
| Improvement Validity | Genuine and sustained improvement Section 3 | (i) Validity, reliability, robustness, and truthfulness | Are improvements genuine and sustained, including after revisions to the update mechanism? |
| Constraint Preservation | Behavioral constraints, alignment, and fairness Section 4 | (ii) Behavioral safety and value alignment; (iii) fairness | Do behavioral requirements remain satisfied across successive revisions? |
| Constraint Preservation | System security, resilience, privacy, and data governance Section 5 | (iv) System security and resilience; (v) privacy and data governance | Are inherited components and information protected during subsequent use? |
| Effective Oversight | Transparency and controllability Section 6 | (vi) Transparency and interpretability; (vii) human control and corrigibility; (viii) accountability and governance | Can revisions, including changes to the update mechanism, be reviewed and corrected? |
| Study and setting | Modified object / reuse | Horizon | Comparison and resource evidence |
| SICA ( Robeyns et al., 2025 ) Claude 3.5 / o3-mini; SWE-bench, LiveCodeBench | Agent code , prompts, tools; revised agents write later edits (archive selection fixed) | 15 self-edits | Initial vs. later agents: 17% 53% at peak on 50 SWE-bench tasks; $7k API; no fixed-updater ablation |
| Agent Plasticity ( Singh et al., 2026 ) Frontier LMs; chess, Go, Hex, NetHack | Tools, skills, notes inherited; – improvement protocol fixed (weights fixed) | 20/40 rounds | Held-out checkpoint tests; gain per dollar , including reflection and rejected edits |
| MASS ( Lee et al., 2026a ) Qwen3.6-27B; finance, robotics, pharmacy | Workflows and weights ; updated model reused as optimizer and evaluator (outer loop fixed) | 2 cycles | Base vs. trained models; external judgments; token efficiency reported, training cost unmatched |
| Hyperagents ( Zhang et al., 2026f ) Claude 4.5; paper review, robotics rewards | Task/meta-agent code ; revised meta-agent reused across domains | 100 searches | Fixed-meta ablation and search controls; 33M self-edit tokens per 100 iterations, evaluation excluded |
| Evo 2 ( Xu et al., 2026b ) Qwen3.8-27B; Polyglot, SWE-bench, LoCoMo | Harness / Proposer–Reflector weights ; trained updater reused in later searches | Repeated ; total not reported | Trained vs. untrained evolver ; parents, executor, search fixed; training excluded from inference cost |
| Study | Tested setting | Horizon / controls | Key finding |
| Behavioral constraints | |||
| Qi et al. (2024) | GPT-3.5 Turbo / Llama-2-7B; 330 prompts, 11 prohibited categories | 1 epoch ; before/after on the same safety test and scoring rule | Harmful compliance after benign tuning |
| Zhao et al. (2026b) | GPT-4o web agent; BrowserART / WebArena | 106 steps ; weights and tests fixed; execution / refusal memories varied | Unsafe actions , but over-refusal |
| Alignment | |||
| Langosco et al. (2022) | CoinRun; relocated coin vs. level completion | Zero-shot ; trained policy and reward fixed | Navigation retained — relocated coin often passed |
| Khalaf et al. (2025) | GPQA; proxy reward vs. answer accuracy | Up to 32 samples ; questions, response pool, reward model fixed | Accuracy peaks then declines with stronger selection |
| Retained form | Trace | Control test |
| Textual memories and skills | Source , active text, retrieval / selection, actual use | Edit / exclude ; test influence remaining in copies |
| Loadable adapters | Source / generator / teacher version ; base and active adapters | Swap / load / scale / ablate under composition |
| Merged parameters | Contributors / merge ; active and derived weights | Verify correction in merged and derived state |
| Attribution | Question | Evidence |
| Technical contribution | Which changes affected the outcome? | Component ablations ; interactions across revisions |
| Operational responsibility | Which duties applied / were fulfilled? | Assigned roles ; available information; recovery actions |
| Governance accountability | Who must explain and remedy? | Authorization / delegation ; review and action records |
| Requirement group | Core signal | Across versions |
| Improvement validity | Independent gains ; variance | Retention / shift ; report accuracy |
| Behavioral safety and alignment | Violation severity | Conflicting or changed goals |
| Fairness | Worst group ; subgroup gains / harms | Population coverage across versions |
| Security and resilience | Attack success ; benign utility | Inherited compromise ; recovery |
| Privacy and data governance | Disclosure / inference / extraction | Residual exposure after deletion |
| Transparency and interpretability | Reconstructable changes | Explanation fidelity after inheritance |
| System setting | What is modified? | Is feedback independent? | What persists after acceptance? | Main evidence gap |
| Coding agents ( Zhang et al., 2026e ; Guo et al., 2026 ) | Agent code, prompts, tests, and scaffolds. | Independence depends on test ownership; protected assessment is needed. | Code, instructions, and generated artifacts. | Safety under the intended deployment conditions. |
| Memory / search agents ( Zhang et al., 2025a ; Lee et al., 2026b ) | Memory contents and designs, retrieval policies, and indexes. | Independence requires protected relevance and coverage checks beyond search feedback. | Memories, indexes, and query behavior. | Privacy, coverage, and resistance to poisoning. |
| Agents with evolving safeguards ( Rosser and Foerster, 2025 ; Cheng et al., 2026a ) | Candidates, policies, harnesses, and guards. | Reassess feedback independence after safeguards change. | Accepted candidates and safety mechanisms. | Protection retained across later versions. |
| Meta-agents (Hyperagents) ( Zhang et al., 2026f ) | The mechanism governing later updates. | Assessment must remain independent of the editable updater. | The revised process for producing future changes. | Quality of subsequent updates under the revised updater. |
| Clinical agents (MedRSI) ( Wu et al., 2026b ) | Tools, registration decisions, and workflows. | Cohort-based registration; independent clinical validation is still required. | Registered tools and workflows; clinical effects if deployed. | Patient-level validity and clinical deployment safety. |
| Embodied agents (RoboFoundry) ( Liang et al., 2026 ) | Skills, context, and recovery procedures. | Tested transfer; independent physical safety and intervention checks are required. | Retained skills and procedures; physical effects when executed. | Physical safety beyond the tasks and real-world trials tested. |
Appendix figures & tables1 asset
Supplementary material from the paper’s appendix.
Appendix
| Source | Full venue or source name | References |
| Preprints and online sources | ||
| arXiv | arXiv preprints | 198 (65.78%) |
| Web | Online model announcements and research essays | 3 (1.00%) |
| OpenReview | OpenReview records without a named proceedings venue | 1 (0.33%) |
| Preprints.org | Preprints.org preprints | 1 (0.33%) |
| Subtotal | 203 (67.44%) | |
Recursive Self-Improvement
Recursive self-improvement studies AI systems that use feedback from their own work to modify and evaluate future versions.
See all 84 papers