How to read METR’s AI task-completion time horizons
The duration uses a human baseline to describe task difficulty. Reliability, task selection and the dashboard’s update status determine what the chart can support.
By SI MicrostudioPublished Sources checked 3 min read (editorial estimate)
Saved reading stays only on this device.
AI-assisted editorial review · Sources checked · Recheck due
The takeaways
METR’s dashboard is no longer actively updated; its last update is 8 September 2026.
A time horizon refers to human task duration at a specified predicted success level.
Use the metric to frame a question about your work, then test that work directly.
Start with the dashboard’s status and definition
METR states that its time-horizon dashboard is no longer actively updated. It shows a last-update date of 8 September 2026. The measure estimates the human task duration at which an agent reaches a specified success probability. Its tasks primarily cover software engineering, machine learning and cybersecurity.
The 29 January TH1.1 release expanded the suite from 170 to 228 tasks and changed evaluation infrastructure. METR reported measured human baselines for only five of its 31 tasks lasting eight hours or more; the others used estimates. The release also discusses sensitivity to task composition.
Suppose a chart reports a two-hour horizon at 50% success. This is an illustrative number, not a current model score. Read it as a fitted prediction about tasks characterized by a two-hour human baseline within the evaluated distribution. It does not provide two hours of guaranteed unattended operation.
Now imagine using that headline to choose an agent for a weekly reporting job. Your job may involve finding a changed spreadsheet, resolving a missing value, obtaining a colleague’s decision and publishing a summary. A duration estimate alone does not tell you which of those steps the evaluation represented.
Write those steps down and identify which outcomes can be checked. For a first trial, you might evaluate the calculation and draft creation while leaving the colleague’s decision and publication with a person. That produces a bounded question you can actually investigate instead of treating an entire job as one benchmark task.
Editorial implications, not an independently measured result.
Editorial interpretation
Turn a chart into a testable work question
Our proposed worksheet has five entries: the cited evaluation version, the task domain, the human baseline, the success threshold and the uncertainty around the estimate. Add the source’s last-update status so a useful historical measurement does not become a claim about every model available today.
Next, describe the consequence of an incorrect result in your own task. An occasional error in a private draft creates a different review burden from an error in a report sent to customers. Choose your acceptable outcome and verification method before deciding which model to trial.
For a superintelligence discussion, define the broader claim separately. A claim about general competence across unfamiliar domains requires evidence from those domains. A forecast about replacing a whole job also needs a description of the work that was omitted from the measurement. The chart can inform the discussion without supplying all of those missing premises.
Editorial implications, not an independently measured result.
The comparison
The table scrolls horizontally on smaller screens.
An editorial worksheet for interpreting a time-horizon claim
Entry
Question to write down
Scope
Which parts of my job resemble the evaluated tasks?
Google’s October walkthrough follows a researcher from protein searches to a candidate for experimental investigation. The useful question is which evidence supports each step.
Liquid AI’s October release gives local-agent builders another model to evaluate. Check the checkpoint, workload and usage conditions before interpreting its benchmark scores.
A tool operation and an independent agent collaboration expose different responsibilities. Map the service first, then check the protocol version and implementation.