AlphaIdeaBench evaluates research ideas against budgets and a 12-dimension rubric
Imagen generada con gpt-image-2.5-sunburst para InferamaSource ↗
01

An evaluation that accounts for available resources

Generating a research idea is not just about proposing something novel. It also matters whether the plan can be carried out with the available time, computing power, and API credit. AlphaIdeaBench addresses this tension with a benchmark designed to compare automatically generated research proposals under explicit budgets, rather than scoring only their novelty or similarity to published work.

The paper was submitted to arXiv on October 24, 2026, and is presented as a preprint. Its abstract describes the design and some results, but does not by itself establish that the conclusions have undergone peer review or been reproduced by other teams. AlphaIdeaBench is therefore best understood as a proposed measurement framework and an initial set of findings, not as a general validation of research agents.

02

One hundred tasks with explicit conditions

AlphaIdeaBench contains 100 tasks: 50 come from workshop calls for papers and 50 from open problems described in survey papers. Each task is paired with a resource budget and a shared proposal format. This structure is intended to make responses comparable against common criteria and within stated limits.

Including a budget changes the evaluation question. A proposal may seem interesting in the abstract while requiring more computing power, time, or API credit than is available. The benchmark makes that distinction part of its analysis, although feasibility scores remain evaluations by the system, not proof that a plan has actually been executed. The available abstract does not give the values of every budget or allow readers to inspect each individual task.

Benchmark components described in the abstract

The composition reported in the abstract conveys the general scope, but it does not replace examining the specific tasks and rules.

ComponentDescription reported
Tasks100 in total
Sources50 workshop calls for papers and 50 open problems from survey papers
ConstraintsEach task is paired with an explicit resource budget
FormatProposals use a shared schema
EvaluationAn LLM-based judge scores 12 dimensions
03

Twelve dimensions for assessing proposals

The AI judge assigns scores across 12 dimensions grouped around validity, novelty, and feasibility. The paper distinguishes four axes of novelty: novelty of the problem, the method, the scenario, and the insight or knowledge contributed. Separating these axes can help prevent a single overall judgment of “originality” from obscuring important differences—for example, between a new research question and a different technique.

Budget feasibility also matters: a proposal that exceeds the assigned resources does not meet the same goal as one that fits within them. Even so, a rubric applied by a model is neither a deterministic control nor proof that a plan can be carried out. Scores depend on how the criteria are defined and how the judge interprets the proposals; the abstract does not provide enough detail to reconstruct all the scoring rules.

04

The judge is compared with reviewer comments

To examine the judge, the study compares its scores on four novelty axes with scores derived from reviewer comments on 600 papers from ICLR 2026, NeurIPS 2025, and ICML 2025. The abstract reports that Gemini 3.7 Flash came within one point of the review-derived score for 94–97% of papers on problem and method novelty. Agreement was relatively lower for scenario novelty.

That percentage describes closeness to a score derived from review comments on the specified axes; it does not mean the judge and reviewers agree on every criterion, nor that the model correctly evaluates any new proposal. The abstract does not say how many reviewers contributed to each paper, how their opinions were aggregated, what exact measure defines “within one point,” or how much reviewers agreed with one another. The comparison therefore offers a limited signal of alignment, not a general certification of quality.

05

Differences between agents and backbone models

The paper compares eight published systems, called harnesses, using a shared backbone, and also compares eight language models within one of those harnesses. According to the abstract, CoI-Agent has the highest overall score, narrowly ahead of SciMON; SciMON leads on method and insight novelty. All eight systems score low on scenario novelty and rarely change the problem setting.

The authors report that the backbone model largely determines which open problem a proposal targets, while the harness influences whether a response addresses one problem or combines several. The abstract also says that weaker models, such as Llama 4 Scout, struggle to follow the evaluated harness’s strategy and score low on budget feasibility. These are results from the specific set and configuration examined; they do not establish a lasting ranking of models or necessarily predict their behavior on other tasks.

A cautious reading of the reported results

These observations summarize comparisons within the benchmark; their scope should not automatically be extended to other contexts.

Reported resultLimited interpretation
CoI-Agent leads on overall scoreIt is the highest overall result reported under the evaluated conditions
SciMON stands out on method and insightLeading on those dimensions does not mean leading on all of them
Scenario novelty is low across harnessesThe benchmark found a shared difficulty on its tasks
The backbone influences which problem is chosenThe observed relationship does not prove the model is the only factor
Llama 4 Scout scores low on budget feasibilityThis result applies to the configuration examined
06

A larger budget can change experimental design

In an additional analysis, the researchers varied only the budget across three topics. For compute-intensive topics, a larger budget changed the experimental setup. For the inexpensive topic, it added tests instead, with less change to the overall design. This observation illustrates why the same increase in resources does not necessarily have the same effect on different problems.

Because this test covers three topics, it cannot establish that the pattern holds across all scientific fields. It does point to a practical distinction when reading proposals: more resources may allow a different kind of experiment when computing costs are a major constraint, while in other cases they may mainly enable additional checks. In either case, a proposal needs independent assessment before it can be treated as an executable plan.

How to assess a budgeted proposal

A benchmark score is a starting point for examining a proposal, not a substitute for scientific or resource analysis.

  1. 01Identify the budget attached to the task and check which resources it includes.
  2. 02Separate novelty of the problem, method, scenario, and proposed insight.
  3. 03Review whether the plan describes experiments compatible with the available resources.
  4. 04Treat the judge’s score as an automated assessment that may require human review.
  5. 05Do not infer scientific results or practical feasibility without examining the plan and its conditions.
07

Scope and limits of the available evidence

AlphaIdeaBench proposes a concrete framework for comparing ideation agents: budgeted tasks, a shared format, a multidimensional rubric, and a partial comparison with review comments. Its potential value lies in making evaluation conditions more explicit and enabling comparisons within a defined set, rather than reducing assessment to a general impression of novelty.

The arXiv record consulted identifies the paper as submitted in October 2026; the material available for this article is the abstract, not an independent verification of every methodological detail. The abstract says that tasks, rubrics, and scores will be released, but does not by itself confirm that those materials are accessible or allow readers to check code, data, or reproducibility. It also does not report the number of reviewers or all the details needed to assess how human scores were constructed. These limits constrain what can be said about the strength and generalizability of the results.

Open questions

  • The abstract does not state how many reviewers contributed or how their comments were aggregated into reference scores.
  • The abstract does not detail the complete agreement measure or the operational meaning of a one-point difference.
  • The consulted record does not confirm whether the tasks, rubrics, scores, data, and code are actually available.
  • Findings about the effect of budgets come from three topics and do not establish that the pattern generalizes to other fields.
  • The consulted record identifies the work as a preprint; it does not confirm peer review or independent replication.
08

Keep exploring

08

Sources consulted

03

Corrections and transparency

If you spot incorrect or outdated information, send us a correction with the page and source we should review.

Submit a correction