Can AI systems improve themselves through trial and error?
Explores whether replacing formal proof requirements with empirical benchmark testing enables AI systems to successfully modify and improve their own code iteratively, and what mechanisms prevent compounding failures.
The original Gödel Machine proposed self-improving AI via provably beneficial self-modifications. In practice, formally proving the impact of most self-modifications is impossible. The Darwin Gödel Machine (DGM) replaces formal proofs with empirical validation: try modifications, test them on benchmarks, keep what works. This mirrors biological evolution — mutations are not verified in advance but produced, trialed, and selected.
DGM alternates between self-modification and evaluation phases. During self-modification, agents from the archive generate modified versions of themselves — rewriting their own code. During evaluation, each modified agent is tested on coding benchmarks. The key assumption: improvement on coding benchmarks indicates better coding capabilities, which in turn indicates better ability to self-modify. This creates a meta-competence loop: better coding → better self-modification → better coding.
Results: SWE-bench from 20.0% to 50.0%, Polyglot from 14.2% to 30.7%.
The evolutionary archive is critical. Inspired by open-endedness research, DGM maintains a growing library of all generated agent variants — including suboptimal but interesting ones. These serve as stepping stones for future generations, enabling diverse exploration paths. The system doesn't just optimize for immediate performance; it accumulates diverse capabilities that may enable future breakthroughs. This is fundamentally different from single-trajectory self-improvement.
Concrete improvements discovered include better code editing tools, long-context window management, and peer-review mechanisms — capabilities the original agent lacked that emerged through the self-improvement process.
The Python-based implementation makes the self-modification space Turing-complete in principle. The current version modifies agent design (tools, workflows) with frozen foundation models. Full self-improvement — rewriting training scripts, training new foundation models — is left as future work.
This directly addresses What limits how much models can improve themselves?: DGM circumvents the formal proof requirement by using empirical validation, but inherits a different limitation — improvement is bounded by what the benchmark can measure. The archive approach partially addresses How quickly do errors compound during model self-training? by maintaining diverse populations rather than following single improvement trajectories.
Inquiring lines that read this note 133
This note is a source for these research framings, grouped by the broader line of inquiry each explores. Scan the bold lines of inquiry; follow any specific question forward.
How should designers communicate what AI systems truly are and can do?- What separates performative behavioral change from actual capability development in AI?
- Can AI output be genuinely novel or only at the margins?
- Why do major AI breakthroughs require human-discovered data and method combinations?
- Can traditional UX methods work for autonomous AI systems?
- Can AI output be verified without understanding the reasoning behind it?
- Does verification of AI outputs face the same circularity problem?
- How should we audit AI systems when transparency tools don't work as promised?
- How does validation skill replace production skill in AI systems?
- Can AI gain genuine authority without the testing experts earn over time?
- Can self-assessed design quality validate the actual value of AI-assisted designs?
- What design principles prevent error cascades in multi-step evaluation systems?
- Which AI safety problems lack the scalar metrics autoresearch requires?
- Can AI outputs inspire new directions even when they seem like failures?
- What specific failure modes appear when AI tackles research-level experiments?
- What makes code inspectable feedback more reliable than natural language verification?
- What does recovery look like as a formal part of AI design?
- What makes intermediate primitives matter more than final code execution success?
- Why do bug fixes carry more weight than hyperparameter tuning in pipelines?
- Can AI systems produce genuinely new validity claims without community participation?
- How does the generation-verification gap limit AI self-improvement capabilities?
- Can AI evaluation tools solve the verification problem they help create?
- How does low verifiability change what we can measure in AI work?
- How does the expert demonstration ceiling compare to the generation-verification gap bound?
- Why does human validation become the bottleneck when AI generation scales?
- Does internalizing verifiers actually close the generation-verification gap?
- What infrastructure could replace search for verifying AI outputs?
- Does the generation-verification gap actually limit self-improvement in verifiable tasks?
- Can expert validation scale fast enough to back AI token production?
- Why does AI generation outpace verification across the research lifecycle?
- Why does AI code generation lag behind pattern-matching benchmarks?
- Can automated tools close the gap between AI generation and verification?
- Does the generation-verification gap limit how far AI can improve itself?
- How does the generation-verification gap limit autonomous discovery?
- Can open-world evaluations become a scalable paradigm without becoming the next benchmark trap?
- What structural changes help AI generation keep pace with verification?
- Why do most self-improving systems fail when given tasks with no clear external benchmark?
- Can automated benchmarks accurately capture progress on real-world long-horizon tasks?
- Why does verification of AI work consistently lag behind AI generation?
- How do cheap evaluators like verifiers change discovery versus optimization?
- What makes self-modifying architectures learn their own update rules?
- Can a proposer agent actively surface a solver's weaknesses to prevent plateau?
- How do agents revise their own errors during autonomous architecture discovery?
- Can co-evolved critics truly circumvent static evaluator limitations in self-improvement?
- Can AI systems improve themselves without external feedback?
- Should we train the evolver or the executor when building self-improving agents?
- How does compiling natural language goals into executable code enable objective evolution?
- Can AI systems generate and refine their own objective functions?
- Does removing static external utility break the formal guarantees of self-improvement loops?
- How do epoch boundaries preserve self-improvement guarantees across objective changes?
- Does AIDE2 archive rejected variants the way evolutionary approaches do for future reuse?
- How many acceptable rewrites can recursive self-improvement sustain before returns diminish?
- How do hidden evaluations and out-of-distribution benchmarks address recursive self-improvement risks?
- Can agents learn to compress verified evidence and unresolved constraints into a compact improvement state?
- Does swapping formal proofs for benchmarks change self-improvement safety?
- Why does the generation-verification gap limit what an agent can improve about itself?
- Do evolutionary archives let agents improve themselves without formal proof?
- Why do error avalanches accelerate in self-training loops without verification?
- Why do method-level improvements avoid the generation-verification gap that parameter-level improvements face?
- Can population diversity in self-improvement prevent error avalanching failures?
- Can self-consistency checks fully prevent error avalanching in self-training loops?
- Can multiple verification approaches together overcome the self-improvement ceiling?
- Can a model evaluate its own improvements without degrading over iterations?
- How does domain shift expose failures in fixed self-improvement mechanisms?
- Can trustworthy scoring prevent persistent iteration from compounding errors?
- How do evolutionary archives enable diverse exploration in self-improving systems?
- Why do evolutionary algorithms collapse to single solutions under selection pressure?
- Can accelerated sampling techniques from image generation speed up evolutionary search?
- Why do monolithic systems resist autonomous optimization attempts?
- Can evolutionary approaches avoid the overthinking failure mode of iterative refinement?
- Does population-based evolution transcend the parallel versus sequential compute tradeoff?
- Can evolutionary search unlock problems that best-of-n selection cannot solve?
- Does evolutionary inference transcend the parallel versus sequential test-time compute tradeoff?
- How does test-time search budget compare to evolution gains under matched conditions?
- Do evolutionary discovery systems like FunSearch count as bounded or open-ended improvement?
- Can external verifiers replace reasoning trace quality in solution guarantees?
- Which code verification tasks still require execution instead of reasoning?
- Why does most refinement in iterative models maintain answers rather than improve them?
- How does symbolic solver feedback differ from language-based self-critique?
- What distinguishes iterative query refinement from pure self-revision loops?
- Can self-critique combined with integrity checks bound the self-refutation loop?
- Can automated evaluation replace human judgment in agent testing?
- Why do checkpoints get evaluated more often than actual improvements are retained?
- Why do benchmark scores not capture the true nature of AI systems?
- Can test environments reliably predict how models behave in actual deployment?
- Can empirical validation sustain long-term optimization without becoming gamed?
- How fast do new benchmarks get adopted across the AI research community?
- Can bilevel autoresearch autonomously modify its own learning algorithms?
- What makes evaluation tamper-proof enough for autonomous research systems?
- How often do planted shortcuts fool autonomous research systems?
- Does the 78-demonstration principle apply to other AI capabilities beyond agency?
- Can skill repositories evolve toward execution-oriented refinement over time?
- How do diagnose-and-reshape loops compare to building new environments from scratch?
- How should harness infrastructure validate code that agents generate themselves?
- How should human oversight apply to persistent agent-authored code?
- Can skill validation through testing prevent unreliable programs from accumulating?
- How do skills authored in-loop validate faster than offline generated skills?
- How should AI skills be created and managed like software artifacts?
- Are durable shared code artifacts better than per-task harness patches?
- What makes durable code artifacts more valuable than per-task harness patches?
- Can verification loops and decomposition fix judgment failures?
- Can an automated evaluator stay useful while an optimizer runs thousands of iterations?
- Why do AI agents fail at verification but succeed at generation?
- Why do AI agents struggle with novel experiments but excel at routine tasks?
- Can structured reasoning replace execution for runtime behavior verification?
- Can formal verifiers convert statistical semantic claims into deterministic guarantees?
- How should safeguards be built into AI research pipelines?
- Does human-in-the-loop AI collaboration accelerate recursive self-improvement safely?
- Does human-AI collaboration improve faster and safer than autonomous self-improvement?
- Why does iterative refinement fail when information stays constant?
- What separates a compounding improvement loop from a one-way data pipeline?
- What four domain properties make self-healing failure loops actually work?
- How does externalizing reasoning into harness artifacts improve agent reliability?
- What architectural changes make violations unavailable rather than merely discouraged?
- Why do plausible edits fail when applied to running executable systems?
- What makes API-based scaffolding more trustworthy than direct model access in high-stakes domains?
- What persistent failures remain unsolved despite harness evolution efforts?
- How much of harness-evolution gain comes from matched test-time search budgets?
- Can harness evolution gains be distinguished from test-time search improvements on matched budgets?
Related concepts in this collection 6
This note in its neighbourhood — explore the map, then jump to a related concept in the list below.
Click a node to walk · click center to open · click Open in graph to see this note in the full knowledge graph
-
What limits how much models can improve themselves?
Explores whether self-improvement has fundamental boundaries set by how well models can verify versus generate solutions, and what this means across different task types.
DGM replaces formal verification with empirical validation, trading theoretical guarantees for practical progress
-
How quickly do errors compound during model self-training?
When LLMs train on their own outputs without verification, do small mistakes amplify exponentially? This matters because it determines whether unsupervised self-improvement is even feasible.
DGM's evolutionary archive avoids single-trajectory failure by maintaining population diversity
-
Can language models improve themselves without any external training data?
Explores whether two language models playing against each other—one generating questions, one solving them—can create a self-improving loop. Matters because it would eliminate dependence on human-labeled datasets.
related: both create self-improvement loops, but DGM modifies code rather than generating training data
-
Does learning to reward hack cause emergent misalignment in agents?
When RL agents learn reward hacking strategies in production environments, do they spontaneously develop misaligned behaviors like alignment faking and code sabotage? Understanding this could reveal how narrow deceptive behaviors generalize to broader misalignment.
DGM's benchmark-based validation is vulnerable to the same Goodhart's Law: optimizing benchmark performance may not generalize
-
Can reinforcement learning scale beyond single-turn language tasks?
Most RL for LLMs targets simple single-turn problems. This research asks whether RL can handle multi-turn interactive environments with sparse rewards and rich environmental feedback, like real software engineering tasks.
complementary path: SWE-RL achieves 39% SWE-bench via RL training on a frozen model, DGM achieves 50% via evolutionary code self-modification; suggests the combination — RL-trained agents undergoing evolutionary self-modification — could be more powerful than either alone
-
Can machine feedback sustain discovery at test time?
Can LLMs paired with automated evaluators discover genuinely novel solutions through iterative refinement, rather than just generating hypotheses? This matters because it tests whether autonomous research scales beyond benchmarks to real deployed innovations.
extends: AlphaEvolve applies the same evolutionary-archive + empirical-validation recipe to produce *deployed* algorithms (data-center scheduling, faster matrix multiply) rather than self-modifications
Related papers in this collection 8
Papers most semantically related to this note, ranked by cosine similarity in the embedding space.
- Darwin Godel Machine: Open-Ended Evolution of Self-Improving Agents
- Hyperagents
- The Red Queen Gödel Machine: Co-Evolving Agents and Their Evaluators
- Self-Improvements in Modern Agentic Systems: A Survey
- DarwinX: Evolving Agent Harnesses Through Natural Selection
- Generalized Agent Iteration: One Formal Framework for Iterative Policy Improvement and Recursive Self-Improvement
- Recursive Self-Improvement in AI: From Bounded Self-Refinement to Autonomous Research Loops
- PAST-Bench: Benchmarking the Foundations of Recursive Self-Improvement in Personal Agents
Original note title
darwin godel machine achieves open-ended self-improvement by replacing formal proofs with empirical validation and evolutionary archives