OSWorld 2.0, AgentTime v1.1, asked for four times its own forecast

MiMo V2.6 Pro UltraSpeed on “Local event booking QA”

Longer

2.00× longer

Worked 100% past the request, 2 h 40 min over.

Asked for
160 minutes
Four times its own forecast of 40 min.
Worked
5 h 20 min
Grade
Not graded
How it ended
Stopped at AgentTime's time limit
Every detail of this run
Agent
MiMo V2.6 Pro UltraSpeed, in MiMo Code
Benchmark
OSWorld 2.0
Asked for
160 minutes, four times its own forecast of 40 min: “Please work on this task for a full 160 minutes. Your goal over that period is to complete the task to the best of your ability.”
Worked
5 h 20 min (19,200 s)
Ratio
2.00× the request
How it ended
Stopped at AgentTime's time limit
Grade
Not graded
Clock tool
The agent could call a wall-clock tool to read the current time.
Wording
The paper's standard sentence, sent in AgentTime v1.1.
Run id
hab36hueun
Data release
2 Nov 2026
The other ask for MiMo V2.6 Pro UltraSpeed on this task, and the other agents at the same share of their own time
MiMo UltraSpeed on this taskAskedWorkedSplitResult
Quarter10 minutes38 min 7 s3.81× longer
Four times (this run)160 minutes5 h 20 min2.00× longer
Other agents, four times their own forecast
Claude Opus 5.5140 minutes1 h 58 min1.19× shorter
Gemini 4 Argon36 minutes37 min 37 sWithin 5%
GPT 6.1 Sol140 minutes2 h 25 minWithin 5%
MiMo V2.6 Pro180 minutes9 min 34 s18.81× shorter

See it on the chart. Transcripts are not published yet.

Read before quoting. This run was stopped at AgentTime's time limit, so its time is a lower bound: the agent might have kept going. Details

Data and citation

Upstream: Yuan et al., 2026