Benchmarks & EvalsMicrosoft
Evidence check
  • Preprint
  • Code/data available
  • Not independently replicated

AI Agents Guess Wrong at Critical Forks 40% of the Time, Taste-Bench Shows

Taste-Bench's 502 decision-fork questions: the best frontier model scores only 59.7%. Later evidence is harder, and bigger reasoning budgets do not help — but taste can be distilled.

Christopher Ort
By Christopher Ort · 2 min read
Share
AI agent at a decision point, making an incorrect choice among several paths, highlighting frequent errors.
Illustration: i10X
On this page
  1. Quick Take
  2. What the study shows
  3. Why it matters: success hides bad forks
  4. Method in brief
  5. What remains open
  6. Context
  7. What it means for agent trainers
  8. About the analysis
  9. i10x Perspective
i10X Quick Take

Quick Take

  1. The finding: On Taste-Bench, the best frontier model answers only 59.7% of decision-fork questions correctly — against a 25% random baseline for the bidirectional protocol.
  2. Harder later: Forks whose deciding evidence appears later in the trajectory are much harder for every model, and a larger reasoning budget does not improve accuracy.
  3. Trainable: Distilling a teacher’s outcome-aware judgment into a student improves decisions on unseen tasks and end-to-end success on held-out SWE-bench Pro tasks.

Long-horizon agents constantly choose which hypothesis to test or which implementation to build on. Researchers from City University of Hong Kong, Microsoft and an independent collaborator call that judgment “taste” — and note that end-to-end success benchmarks never measure it directly.

Stat card: 502 questions, best model 59.7 percent, random baseline 25 percent, human agreement 98.8 percent.
i10X chart based on data from Pan et al. (2026), arXiv:2609.25804, Sections 3–4 (arXiv non-exclusive license).

What the study shows

Taste-Bench mines 502 questions automatically from agent trajectories: 390 engineering (from 2,677 rollouts on 517 SWE-bench Pro tasks) and 112 research (from 1,132 runs on 47 AI R&D tasks). Each question is a fork where one direction later proves better; the model must choose without seeing the aftermath. Human reviewers agree with mined labels 98.8% of the time.

  • Wide model gap: Fourteen models differ widely; none is close to solving the bench.
  • Evidence horizon matters: Accuracy falls as the deciding evidence moves later in the trajectory.
  • More thinking ≠ better taste: Varying reasoning budgets for GPT-5.6 variants did not raise accuracy.
  • Construction quality: Of 4,657 candidate forks, 10.8% passed all filters to become questions.

Why it matters: success hides bad forks

An agent can finish a task after several lucky recoveries from bad choices. Taste-Bench isolates the choices themselves.

Method in brief

Forks mined from parallel attempts and detours; bidirectional evaluation so position bias scores 0%. Code and Hugging Face dataset released.

What remains open

  • Derived from agent runs: Question quality depends on the teacher trajectories.
  • Two domains: Engineering and research; other work may differ.

Context

Complements SWE-bench-style outcome benches. See Benchmarks & Evals and Agents.

What it means for agent trainers

  • Train taste explicitly: Outcome distillation of forks helps.
  • Do not rely on longer CoT alone: Budgets did not fix late-evidence forks.

About the analysis

Researched and written with AI assistance under the editorial responsibility of the i10X News team. The title image is an AI-generated illustration. Read our AI Use Policy. Spotted an error? Request a correction.

This article is based on the full text of the preprint “The Tasteful Agent: Measuring and Improving Taste in Long-Horizon Tasks” (arXiv:2609.25804v2, submitted September 22, 2026). All numbers are taken from the paper’s text, tables and figures; i10X did not rerun the experiments. The paper is distributed under arXiv’s non-exclusive license, so i10X does not reproduce its figures; the chart was drawn by i10X from numbers reported in Sections 3–4.

i10x Perspective

59.7% for the best model on a 25% baseline is not catastrophic — but it means agents still misread nearly half of the forks that decide a run. Teaching taste, not only tools, looks like the next leverage point.

Christopher Ort

Christopher Ort

Christopher Ort handles SEO, AI agent workflows and PR & partnerships at i10x.ai, the all-in-one AI workspace built by i10X Global Pte. Ltd. in Singapore. He is a graduate of Friedrich-Alexander-Universität Erlangen-Nürnberg (FAU). He is the author of “The Style Penalty”, a study published on SSRN that analyses 1,576 evaluation decisions by four frontier AI models to show how AI-written CVs fare in automated hiring screens; the research has been covered by heise online and t3n.

Timeline

What happened before

  1. Partnership

    Microsoft commits multiple billions to Mistral’s European GPU capacity

    With Microsoft · Compute

    reuters.com (source, opens in a new tab)
  2. Release

    MAI-Thinking-1 (7-model MAI family)

    Flagship reasoning model plus MAI-Code-1-Flash, MAI-Image-2.5, MAI-Transcribe-1.5 and MAI-Voice-2.

    microsoft.ai (source, opens in a new tab)
  3. Partnership

    Microsoft and OpenAI amend deal, ending exclusive licence

    With OpenAI · Cloud

    openai.com (source, opens in a new tab)
  4. Partnership

    Microsoft and NVIDIA to invest up to $15B in Anthropic

    With NVIDIA, Anthropic · Compute · $15B

    Microsoft (up to $5B) and NVIDIA (up to $10B) to invest in Anthropic; Anthropic commits to $30B of Azure compute.

    anthropic.com (source, opens in a new tab)
  5. Partnership

    Lambda signs multibillion-dollar deal to deploy NVIDIA GB300 systems for Microsoft

    With Lambda · Compute

    lambda.ai (source, opens in a new tab)
Full Microsoft timeline ›

Editor's picks

  1. Anthropic IPO Filing Reveals Extreme AI Safety Risks
  2. Grok Imagine Odyssey Pilot Exposes AI Video Limits
  3. Anthropic Files S-1 for Nasdaq IPO Under Ticker ANT
  4. Jakarta Agentic AI Milestone Delivers Standardized AI Agents for Java
  5. llm-deepseek Serialization Bug Replays Text After Tool Use