Is METR time horizon still meaningful?
Status:Saturated Checked against the report, 5 November 2026
Verdict
No longer. The best agents outran the task suite, and updates stopped in September 2026.
Why saturated: METR calls values above 16 hours unreliable, and the frontier reached about 17 hours in April 2026. METR stopped active updates on 8 September 2026.[1][1] Time horizons page METR Primary[2][2] Time Horizon 1.1 data file METR Primary
What “Saturated” meansKnown problems
- Only 5 of METR's 228 tasks take a human 16 hours or more (secondary).[3][3] Claude Mythos time horizon OfficeChai Secondary
- METR declined to publish a GPT-5.6 Sol horizon, because it detected unusual cheating.[4][4] GPT-5.6 system card OpenAI Vendor
- METR found reward hacking in 30.4% of o3's RE-Bench runs and calls its counts underestimates.[5][5] Recent reward hacking METR Primary
- No GPT-6, Claude Opus 5.5 or Gemini 4 value exists.[1][1] Time horizons page METR Primary
- METR ran the GPT-5.6 Sol evaluation under an NDA, with OpenAI review of the post.[6][6] GPT-5.6 Sol evaluation METR Primary
- A Stanford preprint finds that difficulty barely rises between 2 and 30 minutes of human time.[7][7] Time horizons refit Nguyen and Fithian Primary
What to look at instead
- Remote Labor Index Status:Still useful Yes. It is one of the few tests where the best agent still fails most tasks.
- Vending-Bench 2 Status:Still useful Yes, as a long-horizon signal. One run per model gives wide error bars.
Where it appears in the report
Chapter 1, Benchmarks
- METR's time horizon doubled every four months, then hit its own ceiling
- Figure 10. The best agents now finish tasks that take an expert most of a working week, half the time
- Table 8. METR 50% and 80% time horizons for the five most recent frontier models in its data file in “Go deeper: METR's data, trend, ceiling and caveats”
Chapter 2, Evaluation science
- Agent scores now depend on how you count cheating and spend tokens
- Figure 9. The agent time horizon grew twentyfold in a year, then cheating broke the measure
- Table 6. Key numbers for agent and long-horizon evaluation in “Go deeper: Agents: key numbers and open problems”
- Open problems in “Go deeper: Agents: key numbers and open problems”
Sources
Copied from the chapter source lists. Each number links back to the source in its chapter.
- [1] Time horizons page, METR. It gives the doubling time, the 16-hour warning and the stop of updates. Primary metr.org Chapter 1, source 11
- [2] Time Horizon 1.1 data file, METR. It gives 50% and 80% horizons per model. Primary metr.org Chapter 1, source 61
- [3] Claude Mythos time horizon, OfficeChai. It reports how few tasks exceed 16 hours. Secondary officechai.com Chapter 1, source 63
- [4] GPT-5.6 system card, OpenAI. It reports METR's view that its Sol time horizon is not robust. Vendor deploymentsafety.openai.com Chapter 1, source 64
- [5] Recent reward hacking, METR. It reports hacking rates on RE-Bench and HCAST. Primary metr.org Chapter 1, source 65
- [6] GPT-5.6 Sol evaluation, METR. It shows how cheat scoring changes the time horizon. Primary metr.org Chapter 2, source 9
- [7] Time horizons refit, Nguyen and Fithian. This preprint refits METR horizons with splines and IRT. Primary arxiv.org Chapter 2, source 86