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× longerWorked 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
Related runs
| MiMo UltraSpeed on this task | Asked | Worked | Split | Result |
|---|---|---|---|---|
| Quarter | 10 minutes | 38 min 7 s | 3.81× longer | |
| Four times (this run) | 160 minutes | 5 h 20 min | 2.00× longer | |
| Other agents, four times their own forecast | ||||
| Claude Opus 5.5 | 140 minutes | 1 h 58 min | 1.19× shorter | |
| Gemini 4 Argon | 36 minutes | 37 min 37 s | Within 5% | |
| GPT 6.1 Sol | 140 minutes | 2 h 25 min | Within 5% | |
| MiMo V2.6 Pro | 180 minutes | 9 min 34 s | 18.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