ReadingResearchRadarInvestment framework
Sign in / Sign up
← Back to reading
NewsTopic · 智能体评估基准Material2 min readDisconfirmAI Editorial

W&B Engineer Wolfram Ravenwolf on Agent Evaluation: From Single Success to Traceable Reliability

In an ai.engineer podcast episode, Weights & Biases engineer Wolfram Ravenwolf introduces the WolfBench evaluation framework. It emphasizes tracing agent scores back to specific configuration conditions (benchmark, sandbox, model service) to distinguish 'lucky success' from 'dependable behavior,' revealing stability issues hidden by average scores through repeated runs and multi-layer tracking.

2026-10-12 01:00 GMT+8

In the video 'From Zero to Leaderboard: Agent Evaluation' published by ai.engineer, Weights & Biases engineer Wolfram Ravenwolf discusses building an agent evaluation pipeline where every score can be traced back to its conditions. He uses a case where an agent repairs a broken git repository and earns a perfect score, but notes that such a run stays out of the default leaderboard because it tested only one task. This distinction forms the core of his methodology: evaluation must go beyond simple averages to examine the source of result reliability.

Ravenwolf presents the WolfBench framework, which compares average, best, and worst runs, as well as tasks solved at least once versus those solved every time. By repeating the same configuration, this approach exposes the gap between a lucky success and dependable behavior. He highlights that the evaluation configuration includes six layers: benchmark, runner, sandbox, agent, model service, and settings. Factors such as versions, provider routing, system prompts, resource limits, and timeouts all affect what the result actually measures.

In a live workflow demonstration, Ravenwolf shows how to launch a Terminal Bench task through Harbor, collect results, filter incomplete runs in a Marimo dashboard, and turn valid runs into an interactive leaderboard. Weave is used to preserve the trajectories behind the bars so reviewers can inspect commands, messages, and failures. He also points out two traps in interpreting results: a cheaper model can consume enough tokens to raise total cost, and greater reasoning effort can lower the score if it leaves too little time to execute commands. Additionally, infrastructure failures need different treatment from genuine task failures, and zero temperature does not guarantee identical runs.

Sign in / Sign up
ReadingResearchRadarInvestment framework

Sources

  • youtube.com↗
Topic

智能体评估基准

智能体评估正经历从“单次任务得分”向“全链路可靠性验证”的范式转移。早期基准如CRAB聚焦于跨设备操作能力,而近期研究揭示现有工具调用基准存在高达18.5%的评估器与人类判断不一致问题,且单次运行结果波动极大。当前核心争议在于:高分是否代表…

6 steps1 piecesUpdated 2026-10-26 10:46

How it got here

  1. 2024-08-14CAMEL AI社区发布CRAB基准,支持同时操控手机和电脑,引入图评估器以细粒度衡量跨环境任务完成率。news.qq.com ↗
  2. 2025-06-04IBM等机构综述120种评估方法,指出当前基准缺乏对成本效率和中间步骤的考量,建议加强细粒度评估。research.ibm.com ↗
  3. 2026-06-30CoreThink AI与斯坦福大学审计发现,主流工具调用基准存在18.5%的评估器-人类判断偏差,LiveMCPBench同配置分数波动达18.9个百分点。arxiv.org ↗

What is still unsettled

  • 如何标准化不同基准间的“可靠性”定义,以便进行横向比较?
  • 在LLM作为评判者(Judge)时,如何有效消除其自身的幻觉与偏见对评估结果的干扰?
  • 企业级部署中,是否应强制要求智能体提供可审计的执行轨迹而非仅输出最终结果?
Read the full topic →
Continue researching →