Nature 658, 1272–1279
Reimagining research papers as interactive and reliable AI agents
Paper2Agent (Miao et al., Nature, 2026)
What the paper does
The Stanford group (Zou and Pritchard labs) built Paper2Agent, a pipeline that turns a published computational paper into an agent you can talk to. It reads the paper and its code repository and packages the method as an MCP server with three parts: tools (the paper's methods as callable functions), resources (manuscript, supplements, data links) and prompts (the paper's multi-step workflows written as instructions). The researcher then connects that server to a general agent, in their case Claude Code running Claude Sonnet 4, and asks for analyses in ordinary language.
The pipeline itself is built from Claude Code agents: one sets up the software environment, one extracts the methods into tools, and a testing agent runs each tool against the paper's own reference outputs until the numbers and figures match. Tools that keep failing are dropped. Each surviving tool carries a link back to the original source code.
Results worth quoting
- The AlphaGenome agent took about 45 minutes and US $14 to build on a laptop, with 22 tools, all passing validation.
- On benchmark questions it scored 98.7% (tutorial-style) and 100% (novel queries), against 82.7% and 78.7% for Claude Code given the raw repository, and 37.3% and 56.0% for Biomni. On 30 open-ended researcher-style questions the margin was 82.7% against 56.7%.
- Across 100 computational biology papers, 74 could be agentified. The failures came from missing code, missing data or model files, broken environments and scripts that only worked for one case.
- The AlphaGenome agent re-examined a published LDL-cholesterol result and favoured SORT1 where the original paper emphasised CELSR2 and PSRC1. The authors present this as the agent re-opening a published interpretation, and they note that all three genes have strong evidence.
- In the psoriasis case, three paper agents (AlphaGenome, an MPRA-coupled CRISPRi screen, a Perturb-seq dataset) were combined. The agent proposed ten validation strategies; the human researcher chose one, and that analysis supported GPR137. The authors say the cross-dataset correlation method was not in any of the source papers.
The authors' own caveats
- "Open-ended scientific reasoning, including hypothesis generation and mechanistic interpretation, remains human-in-the-loop." Researchers select directions and evaluate evidence.
- Benchmarks that check agreement with one reference answer measure faithful execution, not analytical validity; open-ended questions can have several defensible answers.
- Paper agents need maintenance as dependencies change, and they raise security, intellectual property and attribution questions.
Ideas that travel beyond genomics
- "How easily can this paper be turned into an agent?" is a reproducibility test. A quarter of repositories failed for ordinary reasons: incomplete code and undocumented environments.
- An "agent availability" statement alongside data and code availability, which the authors predict journals will start to ask for.
- Validate the agent's tools against known answers before trusting it with new questions. The gain over "Claude Code plus the repo" comes almost entirely from this locked, tested layer.
- Encoded workflows beat clever prompting. The MCP prompts carry the correct order of steps, so the user does not have to know it.
- The division of labour in the discovery case: the agent generates options and executes; the human picks.
Limits for our purposes
The case studies are computational biology with well-maintained Python code. The ten non-biology papers (economics, statistics, astrophysics, game theory) show the pipeline runs elsewhere, but the paper says little about qualitative, archival or humanities research, where "the method" is not a function. All experiments used one model family (Claude). The headline accuracy numbers come from benchmarks the authors constructed.