Use case Sakana AI (with University of British Columbia, University of Oxford, Vector Institute) 2026
The AI Scientist: towards end-to-end automation of AI research
A pipeline that automates the entire scientific life cycle end to end: it creates research ideas, writes code, runs experiments, plots and analyses data, writes the scientific manuscript, and performs its own peer review. A manuscript it generated passed the first round of peer review at a workshop of a top-tier ML conference.
L4Autonomous iterative research (workflow level, not a quality rating) Source: Peer-reviewed source Outcome: Externally validated (partial)
Workflow & human oversight
Iterative idea generation, code execution, experiments, analysis and manuscript evaluation within a research remit. Humans set objectives and compute limits, supervise execution and must review claims before dissemination; automated peer review is not human oversight.
Workflow level is not an evidence score; higher is not better evidence.
Problem
Individual components of the scientific process have been automated before, but a system that autonomously navigates the whole research life cycle - from conception to publication - had remained out of reach. The authors ask how close end-to-end automation now is.
Approach
The AI Scientist is an agentic system built on modern foundation models. It is evaluated in two settings: a focused mode using human-provided code templates as an initial scaffold for a specific topic, and a template-free open-ended mode that uses agentic search for wider scientific exploration.
Outcomes (as reported by the originating team)
The authors report that generated ideas, execution and presentation were of sufficient quality that one manuscript passed the first round of peer review for a workshop whose acceptance rate was 70%, and that both modes produce diverse ideas which are automatically tested, reported on and evaluated (Nature, 2026). The authors flag risks including taxing review systems and adding noise to the literature.
Limitations
Reported results are from ML-research tasks; the peer-review outcome is a single workshop first-round pass, not a full publication. The system's own internal review step is automated and does not substitute for human review. Not independently reproduced.
Reproducibility
The authors publish code at the linked repository (link verified live 2026-10-15). Reproduction or adoption requires budget for running many idea-to-paper cycles, including experiment compute.
Adoption requirements
Frontier model API access with meaningful spend; ML experiment infrastructure; a human to screen outputs before anything leaves the lab, given the authors' own warnings about review load and literature noise.
Comments
No comments yet.
Add a comment
Comments are held for moderation before appearing. Critical or corrective comments are welcome — especially evidence that an entry overstates what has been verified.