This post is a Feynman-style deep analysis of EvoScientist, a self-evolving AI scientist system, published on zhichai.net.
Key points
The problem: static AI scientists
- Most current AI-scientist systems use a fixed pipeline (literature search → idea generation → experiment design → code → report) where each run is independent — the system never learns from past successes or failures.
- The post frames this as a researcher who lives forever on "day one," repeatedly proposing failed ideas and re-debugging old issues.
- Human-in-the-Loop: the AI requires confirmation at every step; humans become a "human API."
- Human-on-the-Loop: the AI explores autonomously; humans supervise and steer at a high level. EvoScientist aims to be a *research buddy*, not a research tool.
- IDE (Idea Direction Evolution): which research directions are promising vs dead ends.
- IVE (Idea Validation Evolution): how to validate ideas efficiently (prototypes, baselines, valuable negative results).
- ESE (Experiment Strategy Evolution): execution-level best practices (preprocessing, architectures, safe hyperparameters).
- Bidirectional memory: a
MEMORY.mdfile is injected into each session (UserProfile, ResearchPreferences, ExperimentConclusion); when token counts exceed a threshold, an LLM extracts new insights back into memory. - Adaptive tool selection: when more than 26 tools are available, an LLM filters a relevant subset;
think_toolandtaskare always kept. - Safe backend:
CustomSandboxBackendoffers a virtual/isolated mode, 300-second timeouts, path traversal detection, dangerous command interception, and system path protection. - MCP integration: config-signature-based connection caching, tool registries for main/sub agents, dynamic server loading.
- OpenClaw: general AI assistant platform; EvoScientist: self-evolving AI scientist with end-to-end research flow; Hermes: message bridging; MetaClaw: meta-learning framework.
- EvoScientist's differentiators: end-to-end research lifecycle, *proactively evolving* persistent memory, multi-agent collaboration as an architectural core, and Human-on-the-Loop philosophy. The systems are complementary — EvoScientist can run on top of OpenClaw infrastructure.
- Memory quality depends on the extraction algorithm; bad extraction can "pollute" rather than improve memory.
- Coordination cost across six agents requires careful prompt design.
- Sandbox safety restricts some experiment types.
- Future: deeper memory compression, cross-instance knowledge transfer, finer-grained agent specialization.
- 🏆 ICAIS 2025 Best Paper and Review Award
- 🏆 Best AI-Generated Paper
- 🥇 1st place, DeepResearch Bench II
- 🥇 1st place, AstaBench Code & Execution and Data Analysis
- GitHub: https://github.com/EvoScientist/EvoScientist
- Technical report: arXiv:2603.08127
Human-on-the-Loop vs Human-in-the-Loop
Six specialized agents
| Agent | Role | |---|---| | planner-agent | experiment planning (no searching, no implementation) | | research-agent | literature research via Tavily | | code-agent | code implementation | | debug-agent | diagnosing and fixing errors | | data-analysis-agent | visualization, statistics, interpretation | | writing-agent | report/paper writing |Constraints are deliberate: limiting each agent's scope prevents goal drift and enforces clarity of collaboration.
Seven-stage research lifecycle
research-ideation → idea-tournament → paper-planning → experiment-pipeline → paper-writing → paper-review → paper-rebuttalThree-layer memory evolution
Technical implementation
Comparison with OpenClaw / Hermes / MetaClaw
Core insights
1. Memory is the foundation of intelligence — without cumulative learning, LLM intelligence stays shallow. 2. Specialization enables collaboration — clear role boundaries can outperform one all-purpose agent. 3. Constraints breed creativity — restricting agents forces clarity.Limitations and future directions
Recognition
Links: