🧬 For agents to evolve themselves safely, the protocol itself needs a redesign — this work fills the pieces missing from MCP and A2A with a self-evolution protocol. Title: Autogenesis: A Self-Evolving Agent Protocol URL: 🧬 Overview The Autogenesis Protocol (AGP) lets LLM agents dynamically improve their own prompts, tools, and policies during execution. Its central idea is to decouple "what evolves" from "how evolution occurs." ❓ Challenges Solved Existing protocols (Anthropic's MCP, Google's A2A) standardize connectivity and invocation but lack the primitives evolution needs. ・Resources stay tightly coupled to agent code ・No version control or rollback for evolutionary steps ・Heuristic edits, with no standardized operators forming a rigorous control loop 💡 Methodology & Approach AGP has two layers. ・RSPL: models prompts, agents, tools, environments, and memory as "registered resources" with explicit state, lifecycle, and versioned interfaces ・SEPL: formalizes evolution as typed, composable operators, routing every change through RSPL so it's versioned and reversible On top, the AGS system runs sub-agents concurrently on an Agent Bus and, when traces signal failures, self-improves via a Reflect → Select → Improve → Evaluate → Commit loop. 🎯 Use Cases It fits building agents that need long-horizon planning and diverse tool use. Because improvements keep an auditable lineage and can be rolled back, you can run self-evolution safely while avoiding brittle glue code. 📊 Results ・Science & math: weaker models gain most. gpt-4o improves +100% on AIME25, gpt-4.1 +71.38% on AIME24, while saturated strong models see small gains (ceiling effects) ・GAIA: Test 79.07% → 89.04% (+12.61%), with +33.34% on the hardest Level 3 ・Code generation: C++ pass rate 79 → 99, time-limit errors 9 → 0, runtime efficiency +46.4%. Jointly evolving prompts and outputs worked best #AIAgents# #SelfEvolution#