# Agentic AI systems for scientific discovery

- Authors: Bin Feng, Peter Walther, Leili Zhang, et al., Philippe Schwaller, Alán Aspuru-Guzik, Zhiling Zheng
- Venue: Nature Reviews Methods Primers 6:81
- Published: 2026-10-22
- Source: https://doi.org/10.1038/s43586-026-00534-y

# Agentic AI systems for scientific discovery (Feng et al., *Nat Rev Methods Primers*, 2026)

## What the paper is

A methods primer from a large chemistry and materials group (Aspuru-Guzik, Schwaller, Zheng and others). It treats agentic AI as **a research method with its own standards for design, validation and reporting**, in the way a primer would treat mass spectrometry. Its examples lean towards chemistry, materials and self-driving labs, but the reporting and validation sections apply to any field.

## The framework in brief

- An **agentic system** is one or more agents, the workflow that organises them, and the environment they act in (data, software, instruments, people). Agency is a **continuum**, not a yes/no property: how much discretion over actions, how much effect on the world, how long the task runs, how persistent the goals and state are.
- Three families: **cognitive** agents (literature, reasoning, computation), **embodied** agents (instruments and robots) and **collaborative** agents (coordination among agents and people).
- Building blocks: a **profile** (often a versioned Markdown file, as in Claude Code), perception, tools (often via MCP), and **memory** (Markdown files for small structured knowledge; vector stores or graphs for large corpora). They explicitly name Claude Code, Codex, Gemini CLI, OpenCode and **reusable skills folders** as the practical form.
- The worked example (lipid nanoparticle formulation) is essentially a repository workspace with skills, data files and a results spreadsheet. **Human approval is reserved for irreversible, safety-critical or physical actions.**

## The parts most useful for training

**Staged validation (Table 2).** Check outputs in order: internal (is it coherent, stable across runs, and is every claim traceable to a source or tool output?), then computational (benchmarks, simulations), then experimental. Cheap internal checks catch most obvious failures.

**Separate utility from evidence.** An output can usefully steer the next step long before it is evidence for a conclusion. Ungrounded outputs may be kept as hypotheses but must be labelled as unsupported.

**Report the degree of autonomy honestly.** Say who set the goal, chose the tools, fixed failures, approved irreversible actions and picked which outputs to validate. Most reported "autonomous" systems are a mix of model capability, design and human scaffolding.

**Run it more than once.** Agents are stochastic and path-dependent; showing only the best run overstates capability. The primer distinguishes **technical replicates** (same configured system, same prompt, again) from **independent replicates** (rebuild the system from its documentation and rerun everything).

**Reproducibility record.** Code and data are not enough. Record prompts, tool versions and interfaces, memory and retrieval set-up, intermediate steps, model versions with access dates, and every human intervention. **Treat tools as lab instruments** and document them as such. Undocumented manual repair, post hoc selection of candidates and silent changes to the search space are named as threats to reproducibility.

**Named failure modes,** each with a test or mitigation:

- *Error accumulation* over long chains; mitigated by separating planning from execution and replanning.
- *Mirage reasoning:* fluent conclusions from evidence that was never supplied. **Test it by removing or altering the evidence and checking whether the conclusion changes.**
- *Inherited bias* from training data; limited by randomisation and blinding of which conditions get tested.
- *Context saturation:* in long runs the original protocol is silently summarised away and the agent quietly breaks a constraint set at the start.
- *Tool misuse:* wrong tool, wrong parameters, wrong stage.
- *Multi-agent coordination:* adding agents can make things worse.
- *Prompt injection* through material the agent reads (web pages, supplementary files, database fields).

**Accountability.** An agent cannot be held responsible; named researchers sign off. Also flagged: energy cost (use smaller models for routine steps) and inequity of access.

## Limits for our purposes

Written from the perspective of experimental natural science and lab automation. It says little about the everyday case of one researcher with a coding agent and a laptop, which is most of Dominik's audience, and almost nothing about qualitative or humanities research. The principles transfer; the examples need replacing.
