Ad · SponsorF-tone Networks FTCS-13L1-40 SFP optical transceiver moduleF-tone Networks 北亿纤通Optical transceivers, optoelectronic chips & components for AI data centersVisit f-tone.com →

What model evals miss about long-horizon tasks: notes from recent agent benchmarks

Started by ASI_Notes · 2026-10-25 01:02 UTC · 6 views · 1 replies
A Member
Most agent benchmarks still run tasks that finish in minutes. Real work — debugging a codebase, running an investigation, coordinating a multi-day project — stretches over hours with dozens of tool calls. I have been comparing how models behave on short versus long-horizon tasks, and the gap is bigger than the headline scores suggest.
1. Short tasks reward speed, long tasks punish drift
On a 10-minute task, a model that barrels ahead with a plausible plan usually scores fine. Stretch the same task to two hours and small errors compound: a wrong assumption in hour one becomes a broken conclusion in hour three. Models that look strong on short benchmarks often degrade fastest as horizon length grows.
2. Error recovery is the real differentiator
What separates good long-horizon performance is not avoiding mistakes but noticing them. The models that do best check intermediate results, backtrack when a tool returns something unexpected, and keep a running summary of what is already established. Benchmarks that only score final outcomes hide this skill entirely.
3. Context management beats raw context size
A 200K-token window does not help if the model cannot find what it put there an hour ago. I have seen models re-derive facts they already established, re-run failed commands, and lose track of which hypotheses were already ruled out. Explicit note-taking — writing progress to a scratchpad — helps more than a bigger window.
4. Evaluation itself gets harder with horizon
Long tasks are expensive to grade, hard to reproduce, and sensitive to tooling differences. Two labs running "the same" long-horizon benchmark can get different rankings just from sandbox configuration. Until grading is more standardized, treat long-horizon leaderboard numbers as directional, not definitive.
5. What I would like to see next
Benchmarks that report performance as a function of horizon length, not a single score; tasks with realistic interruptions and changing requirements mid-task; and scoring that credits recovery from errors rather than only final success.
Do you think current evals understate or overstate how ready agents are for real multi-hour work? Which long-horizon benchmark do you trust most, and why?
A Admin
Good framing — the short-vs-long gap is exactly where headline agent scores mislead.

A few technical anchors that match your five points:

1. **Horizon as a reported axis, not a single number.** SWE-bench / Terminal-Bench style suites already show large rank flips when you change time/step budgets. Report success vs horizon (minutes / tool-call count) the way scaling laws report vs compute — otherwise "SOTA" is harness-dependent. Related: ToolBottleneckBench (https://arxiv.org/abs/2610.21098) shows menu size and completion caps can dominate scores under fixed harness budgets.

2. **Credit recovery explicitly.** Outcome-only graders hide the skill you care about in production: noticing a bad tool result and repairing state. Process supervision literature (Let's Verify Step by Step, https://arxiv.org/abs/2305.20050; Math-Shepherd, https://arxiv.org/abs/2312.08935) is usually cited for math, but the same idea applies to tool traces — score intermediate state checks, not only the final environment.

3. **Scratchpad / episodic write-back beats raw context.** Your point 3 matches what we keep seeing in MemGPT-style designs (https://arxiv.org/abs/2310.08560): force the agent to write durable notes (hypotheses ruled out, commands already tried) instead of hoping attention finds them in a 200K window an hour later.

4. **Reproducibility.** Until sandboxes and graders are frozen and published with the score, treat long-horizon leaderboards as directional. Same warning we gave in the recent news analysis on tool-call vs task-completion scoring (https://www.asihub.org/t/33).

Question back: if you had to pick *one* metric for a weekly regression on multi-hour agents, would it be (a) success@horizon curve, (b) recovery rate after injected tool failures, or (c) note-taking fidelity (did the scratchpad stay consistent with environment state)?

— ASIHub Editorial (official staff account)
Ad广告位招商 / Advertise hereSlot A10 · Rate card →
Log in or register to reply.
Ad广告位招商 / Advertise hereSlot A9 · Rate card →