EvoScientist

EvoScientist aims to harness vibe research by enabling self-evolving AI scientists that autonomously explore, generate insights, and iteratively improve. It is designed to be opinionated and ready to use out of the box, offering a living research system that grows alongside evolving agent skills, toolsets, and memory bases. Moving beyond traditional human-in-the-loop systems, EvoScientist adopts a human-on-the-loop paradigm, where AI acts as a research buddy that co-evolves with human researchers and internalizes scholarly taste and scientific judgment.

🏆 Awards & Recognition

Best Paper & Appraisal Award

AI-Generated Best Paper

#1 on DeepResearch Bench II

#1 on DeepResearch Bench

#1 on AstaBench Code & Execution

#1 on AstaBench Data Analysis

⚡ Unified Control, Different Surfaces

✨ Features

• 🤖 Multi-Agent Team — 6 sub-agents (plan, research, code, debug, analyze, write) working in concert.
• 🧠 Self-Evolving Memory — User profile and observations auto-distilled each turn, growing across sessions.
• 🌐 Multi-Provider — Anthropic, OpenAI, Google, MiniMax, NVIDIA — one config to switch.
• 📱 Multi-Channel — CLI as the hub; Telegram, Slack, Feishu, WeChat, and more — one agent session.
• 🖥️ Desktop WebUI (beta) — Workspace-panel web app, one terminal via --ui webui.
• 🔬 Scientific Workflow — Intake → plan → execute → evaluate → write → verify.
• 🔄 Code Generation Modes — More Effort (iterative refinement), continuously improving code quality.
• ⚡ Adaptive Tools — Per-turn tool selection keeps only relevant tools visible, reducing noise.
• ✂️ Context Editing — Dynamic system prompt rewriting based on conversation state.
• 🔌 MCP & Skills — Plug in MCP servers or install skills from GitHub on the fly.

[!TIP] Looking for ready-to-use research skills? Check out EvoSkills — powered by EvoScientist's engine and installable skills, the entire end-to-end research lifecycle is covered out of the box. EvoSkills are also compatible with other CLI coding agents.

🔥 News

• [03 Jun 2026] 🥈 Ranked #2 overall — and 🥇 #1 among GPT-5.4-based agents — on ResearchClawBench (Agent Mode)! Leaderboard 👈
• [18 Apr 2026] 🥇 Ranked #1 on DeepResearch Bench at submission time! Leaderboard 👈
• [13 Apr 2026] 🥇 Reclaimed #1 on DeepResearch Bench II at submission time! Leaderboard 👈
• [26 Mar 2026] 🥇 Ranked #1 on AstaBench Data Analysis at submission time! Leaderboard 👈
• [25 Mar 2026] 🥇 Ranked #1 on AstaBench Code & Execution at submission time! Leaderboard 👈
• [13 Mar 2026] 🚀 EvoScientist officially debuts!
• [11 Mar 2026] ⛳ Technical Report is live! Check it out 👈
• [06 Mar 2026] 🥇 Ranked #1 on DeepResearch Bench II at submission time! Leaderboard 👈
• [24 Nov 2025] 🏆 6/6 accepted at ICAIS 2025 AI Scientist Track — Best Paper & AI Reviewer's Appraisal Award! Details 👈

📖 Table of Contents

• 📦 Installation
• 🔑 Configuration
• ⚡ Quick Start
• 🍪 Examples & Recipes
• 🔌 MCP Integration
• 📱 Channels
• 📚 Acknowledgments
• 🎯 Roadmap
• 🌍 Project Roles
• 🤝 Contributing
• 📝 Citation

📦 Installation

[!TIP] Requires Python 3.11+ (< 3.14). We recommend uv or conda for dependency management and virtual environments. Prefer to skip a local Python install entirely? Jump to 🐳 Docker.

curl -LsSf https://astral.sh/uv/install.sh | sh

Quick Install

uv tool install EvoScientist

[!NOTE] To update an existing installation to the latest version, use uv tool upgrade:

uv tool upgrade EvoScientist

Or install into the current environment instead:

uv pip install EvoScientist

Latest from GitHub

To get the latest patches before a PyPI release:

uv pip install git+https://github.com/EvoScientist/EvoScientist.git

Development Install

git clone https://github.com/EvoScientist/EvoScientist.git
cd EvoScientist
uv sync --dev

enable pre-commit hooks:

uv run pre-commit install

conda create -n EvoSci python=3.11 -y
conda activate EvoSci
pip install -e ".[dev]"

pip install EvoScientist          # quick install
pip install -e ".[dev]"           # development install

uv pip install "EvoScientist[telegram]"     # Telegram
uv pip install "EvoScientist[discord]"      # Discord
uv pip install "EvoScientist[slack]"        # Slack
uv pip install "EvoScientist[wechat]"       # WeChat
uv pip install "EvoScientist[qq]"           # QQ
uv pip install "EvoScientist[feishu]"       # Feishu
uv pip install "EvoScientist[all-channels]" # everything

git pull && uv sync --dev

🐳 Docker

A pre-built image is published to GitHub Container Registry with everything evosci onboard would otherwise install for you:

• Python 3.11, EvoScientist, and the cross-platform messaging channels (i.e., EvoScientist[all-channels])
• uv — used by the MCP registry to install Python MCP servers on demand
• Node.js 24 LTS + npx — required by the majority of MCP servers

The iMessage channel isn't usable from the container — it requires the imsg CLI talking to macOS's Messages.app, which is host-OS-specific. Run EvoScientist directly on macOS if you need iMessage.

Running EvoScientist in a container also sandboxes the agent's shell access — file edits and shell commands stay confined to volumes you explicitly mount.

docker run -it --rm \
  --env-file .env \
  -v "$(pwd)/workspace:/workspace" \
  -v evosci-data:/home/evosci/.evoscientist \
  ghcr.io/evoscientist/evoscientist:latest

What the mounts are for:

[!IMPORTANT] The image runs as a non-root user (evosci, UID 1000). For the ./workspace bind mount, the host directory must be writable by that UID. If your host user ID differs, either chown -R 1000:1000 ./workspace once, or pass --user "$(id -u):$(id -g)" on every docker run so the container takes on your UID.

Or use docker compose (a starter docker-compose.yml is included):

docker compose run --rm evoscientist

To build the image locally instead of pulling:

docker build -t evoscientist:dev .

[!NOTE] Not bundled — install on demand by deriving from the image:

• stt (speech-to-text via faster-whisper) and oauth (ccproxy-api)
• TinyTeX / LaTeX (pdflatex, latexmk) for paper-writing skills

FROM ghcr.io/evoscientist/evoscientist:latest

# Python extras
USER root
RUN uv pip install --python /opt/venv/bin/python "EvoScientist[stt,oauth]"
USER evosci

# TinyTeX
# The official install method is `curl | sh`; if you'd rather not
# pipe an unpinned remote script into a shell, fetch a specific TinyTeX
# release tarball from https://github.com/rstudio/tinytex-releases, verify
# its checksum, and extract to /home/evosci/.TinyTeX instead.
RUN curl -sL https://yihui.org/tinytex/install-bin-unix.sh | sh \
 && /home/evosci/.TinyTeX/bin/*/tlmgr install latexmk

🔝Back to top

🔑 Configuration

The easiest way to configure API keys is the interactive wizard:

EvoSci onboard

[!TIP] It walks you through provider selection, key validation, model choice, and workspace mode. Supports OAuth sign-in for CLI coding agent subscribers — no API key needed.

# Pick one LLM provider
export ANTHROPIC_API_KEY="sk-..."   # Claude  — console.anthropic.com
export OPENAI_API_KEY="sk-..."      # GPT    — platform.openai.com
export GOOGLE_API_KEY="AI..."       # Gemini  — aistudio.google.com/api-keys
export MINIMAX_API_KEY="sk-..."     # MiniMax — platform.minimaxi.com (China, default) or platform.minimax.io (Global)
export MINIMAX_BASE_URL="https://api.minimax.io/anthropic"  # only needed for Global keys (default: https://api.minimaxi.com/anthropic)
export NVIDIA_API_KEY="nvapi-..."   # NIM    — build.nvidia.com

# Web search (optional)
export TAVILY_API_KEY="tvly-..."    # app.tavily.com

cp .env.example .env  # then fill in your keys

🔝Back to top

⚡ Quick Start

EvoSci  # or EvoScientist — interactive mode (TUI by default)

Run EvoSci -h for all CLI options.

[!TIP] Prefer a browser? Run EvoSci --ui webui for the web workspace UI (beta). Need to copy long outputs? Use --ui cli for classic mode where native terminal copy works freely. On macOS, iTerm2 users can also hold ⌥ Option while dragging to select, then ⌘+C.

EvoSci                            # interactive mode (TUI by default)
EvoSci -p "your question"        # single-shot mode
EvoSci --workdir /path/to/project # open in a specific directory
EvoSci -m run                     # isolated per-session workspace
EvoSci --ui cli                   # classic CLI (lightweight)
EvoSci --ui webui                 # browser workspace UI (beta, needs Node/npx)
EvoSci serve                      # headless mode — channels only, no interactive prompt
EvoSci deploy                     # standalone LangGraph server for external UIs / SDK clients

EvoSci config set ui_backend webui   # persist; or one-off with `EvoSci --ui webui`
EvoSci                               # opens http://localhost:4716
EvoSci config set webui_port 4800    # change the front-end port (must differ from the langgraph dev port)

# Per-session: auto-approve via CLI flag
EvoSci --auto-approve
EvoSci -p "query" --auto-approve

# Persistent: set in config (applies to all future sessions)
EvoSci config set auto_approve true

# Or allow only specific command prefixes
EvoSci config set shell_allow_list "python,pip,pytest,ruff,git"

# Persistent: set in config
EvoSci config set enable_ask_user false

# Re-enable
EvoSci config set enable_ask_user true

from EvoScientist import EvoScientist_agent
from langchain_core.messages import HumanMessage
from EvoScientist.utils import format_messages

thread = {"configurable": {"thread_id": "1"}}
last_len = 0

for state in EvoScientist_agent.stream(
    {"messages": [HumanMessage(content="Hi?")]},
    config=thread,
    stream_mode="values",
):
    msgs = state["messages"]
    if len(msgs) > last_len:
        format_messages(msgs[last_len:])
        last_len = len(msgs)

🔝Back to top

🍪 Examples & Recipes

A curated collection of official examples, advanced usage patterns, and community-contributed recipes to help you get the most out of EvoScientist.

👉 Browse all examples & recipes

🔝Back to top

🔌 MCP Integration

Add external tools via MCP servers with a single command:

# Usage
EvoSci mcp add <name> <command> [-- args...]

# Example
EvoSci mcp add sequential-thinking npx -- -y @modelcontextprotocol/server-sequential-thinking

[!TIP] For command options, config fields, tool routing, wildcard filtering, and troubleshooting, see the MCP Integration Guide.

🔝Back to top

📱 Channels

Connect messaging platforms so they share the same agent session as the CLI:

# Usage
EvoSci channel setup <channel>

# Example
EvoSci channel setup telegram

Multiple channels can run concurrently — comma-separate names in the config:

channel_enabled: "telegram,slack,feishu,qq"

The channel can also be started interactively with /channel in the CLI session.

[!TIP] For per-channel setup guides, capability matrix, architecture details, and troubleshooting, see the Channel Integration Guide.

🔝Back to top

📚 Acknowledgments

This project builds upon the following outstanding open-source works:

• LangChain — A framework for building agents and LLM-powered applications.
• DeepAgents — The batteries-included agent harness.

We thank the authors for their valuable contributions to the open-source community.

🔝Back to top

🎯 ᯓ➤ Roadmap

Coming soon:

• [x] 🖥️ Full-screen TUI and classic CLI interfaces
• [x] 📻 EvoMemory v1.0 shipped
• [x] ⚒️ 200+ predefined skills built in
• [x] 🧩 Built-in research-lifecycle skills shipped
• [x] 👋 Human-in-the-loop action approval
• [x] 🦾 Agent-initiated human clarification
• [x] 📑 Technical report on the way
• [x] 🔐 OAuth sign-in (CLI coding agent subscribers)
• [x] 📺 Web app with workspace UI (beta)
• [ ] 📹 Demo and tutorial in the works
• [ ] 📊 Benchmark suite to be released
• [ ] ⏰ Scheduled tasks for the core system planned

Stay tuned — more features are on the way!

🔝Back to top

🌍 Project Roles

Core Contributors

Xi Zhang

Yougang Lyu

Dinos Papakostas

Yuyue Zhao

Ziheng Zhang

Xiaohui Yan

Contributors

Jan Piotrowski, Wiktor Cupiał, Jakub Kaliski, Jakub Filipiuk, Xinhao Yi, Shuyu Guo, Andreas Sauter, Wenxiang Hu, Jacopo Urbani, Zaiqiao Meng, Jun Luo, Lun Zhou

Xiaoyi DeepResearch Team and the wider open-source community contribute to this project.

For any inquiries or collaboration opportunities, please contact: [email protected]

🔝Back to top

🤝 Contributing

We welcome contributions from developers, researchers, and AI coding agents at all levels. Our Contributing Guidelines are designed for both humans and AI agents — covering architecture, patterns, extension guides, and code standards to help you contribute safely and effectively.

👥 Community Contributors

⚗️ Join the EvoScientist community to discuss AI-driven research, share experiment results, and help shape the future of automated scientific discovery.

• Discord — Ask questions, share findings, and collaborate with researchers and developers in real-time.

• WeChat — Connect with our Chinese-speaking research community.

  

Every contribution brings us one step closer to a future where AI accelerates scientific breakthroughs for all of humanity.

🔝Back to top

📝 Citation

If you find our paper and code useful in your research and applications, please cite using this BibTeX:

@article{evoscientist2026, 
  title={EvoScientist: Towards Multi-Agent Evolving AI Scientists for End-to-End Scientific Discovery}, 
  author={Yougang Lyu and Xi Zhang and Xinhao Yi and Yuyue Zhao and Shuyu Guo and Wenxiang Hu and Jan Piotrowski and Jakub Kaliski and Jacopo Urbani and Zaiqiao Meng and Lun Zhou and Xiaohui Yan}, 
  journal={arXiv preprint arXiv:2603.08127}, 
  year={2026} 
}

🔝Back to top

📜 License

This project is licensed under the Apache License 2.0 - see the LICENSE file for details.

🔝Back to top