Key papers
Reading notes on 5 papers about agents doing research: what each paper does, what is worth quoting and where it stops.
Nature Reviews Methods Primers 6:81
Agentic AI systems for scientific discovery
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.
Nature 658, 1272–1279
Reimagining research papers as interactive and reliable AI agents
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.
Nature 655, 497–505 (page range taken from the running footers)
A multi-agent system for automating scientific discovery
A FutureHouse and Fordham team describes Robin, a workflow of language agents that, given a disease name, proposes in vitro assays and drug candidates and then analyses the laboratory data a human produces. Two literature agents built on PaperQA2, Crow (short reviews) and Falcon (long reports on each candidate), feed an LLM-judged pairwise tournament that ranks assays and candidates. A data analysis agent, Finch, writes and runs Jupyter notebooks on raw data (flow cytometry, RNA sequencing). Robin uses o4-mini to synthesise literature and Claude 3.7 Sonnet as judge. The Methods say Robin "almost always called tools in the same order", so the paper's experiments were run as a fixed notebook sequence rather than free agent choice.
Nature 655, 487–496 (page range taken from the running footers)
Accelerating scientific discovery with Co-Scientist
A Google group (with collaborators at Stanford, Houston Methodist, Imperial and Sequome) describes Co-Scientist, a multi-agent system built on Gemini 2.0 that takes a research goal written in natural language and returns ranked research hypotheses and proposals. Agents have separate jobs: Generation, Reflection (acts as peer reviewer, with web search), Ranking (runs an Elo tournament of pairwise "scientific debates"), Proximity (clusters similar ideas), Evolution (writes new hypotheses from the best ones; it does not edit existing ones) and Meta-review (summarises recurring review criticisms and appends them to the other agents' prompts). A Supervisor agent schedules them on a task queue. Scientists can supply ideas, reviews and feedback through a chat interface.
Nature 651, 914–919
Towards end-to-end automation of AI research
A team from Sakana AI, the University of British Columbia, the Vector Institute and Oxford (FLAIR) describes The AI Scientist, a pipeline of language-model agents that proposes a machine-learning research idea, checks it against the literature (Semantic Scholar), writes and runs the experiments, plots the results, writes a LaTeX paper and then has it reviewed by a second component, The Automated Reviewer. It only does computational experiments in machine learning. There are two modes: a template-based one that extends human-supplied starter code, and a template-free one that writes its own code through a parallel tree search (Methods). The template-free version used OpenAI o3 for ideas and code critique, Claude Sonnet 4 for code, GPT-4o for figures and best-first node selection, and o4-mini for review. A full template-free run takes "from several hours to over 15 h".