50% Task Horizon — Claude Mythos Preview (Apr 2026)
~17.4 hours
METR Time Horizon 1.1 evaluation (provisional)
vs. 9 seconds in 2020
Historical Doubling Rate
~6.2 months
All-time METR TH1.1 curve fit (187.8 days)
Accelerated to ~4.2 months since 2023 (128.7 days)
50% Task Horizon — GPT-5.4 (Mar 2026)
5h 42m
METR Time Horizon 1.1 evaluation
~86× increase since GPT-4 in 2023
Total Increase (2020 → 2026)
~4 orders of magnitude
9 seconds → 17.4 hours
~7,000× in absolute terms

Data

AI Autonomous Task Time Horizon — How Long Frontier Models Work Without Human Intervention (2020–2026) — source data. METR (Model Evaluation & Threat Research); arXiv:2503.14499 (Kwa et al., March 2025).
Model Organisation Date 50% Task Horizon Notes Source
Claude Mythos Preview (early) Anthropic Apr 2026 17h 25m Provisional; exceeds METR's ~16h reliable-measurement ceiling. METR's own public estimate: at least 16h (95% CI 8.5-55h) METR Time Horizon 1.1 dataset
GPT-5.4 OpenAI Mar 2026 5h 42m TH1.1 point estimate METR Time Horizon 1.1 dataset
Gemini 3.1 Pro Google DeepMind Feb 2026 6h 24m TH1.1 point estimate METR Time Horizon 1.1 dataset
GPT-5.3-Codex OpenAI Feb 2026 5h 50m TH1.1 point estimate METR Time Horizon 1.1 dataset
Claude Opus 4.6 Anthropic Feb 2026 11h 59m TH1.1 point estimate; revised down from an initial ~14.5h estimate after METR's March 2026 regularisation correction METR Time Horizon 1.1 dataset
GPT-5.2 OpenAI Dec 2025 5h 52m TH1.1 point estimate METR Time Horizon 1.1 dataset
Claude Opus 4.5 Anthropic Nov 2025 4h 53m TH1.1 point estimate METR Time Horizon 1.1 dataset
Gemini 3 Pro Google DeepMind Nov 2025 3h 44m TH1.1 point estimate METR Time Horizon 1.1 dataset
GPT-5 OpenAI Aug 2025 3h 23m TH1.1 point estimate METR Time Horizon 1.1 dataset
Claude Opus 4 Anthropic May 2025 1h 40m TH1.1 point estimate METR Time Horizon 1.1 dataset
o3 OpenAI Apr 2025 2h 0m TH1.1 point estimate METR Time Horizon 1.1 dataset
Claude 3.7 Sonnet Anthropic Feb 2025 1h 0m TH1.1 point estimate METR Time Horizon 1.1 dataset
o1 OpenAI Dec 2024 39 min TH1.1 point estimate METR Time Horizon 1.1 dataset
Claude 3.5 Sonnet Anthropic Oct 2024 21 min TH1.1 point estimate; supersedes the earlier ~40min HCAST-only estimate from the March 2025 paper METR Time Horizon 1.1 dataset
GPT-4o OpenAI May 2024 7 min TH1.1 point estimate METR Time Horizon 1.1 dataset
GPT-4 OpenAI Mar 2023 4 min TH1.1 point estimate METR Time Horizon 1.1 dataset
GPT-3 (davinci-002) OpenAI Mid-2020 9s METR's earliest TH1.1 baseline; not a contemporaneous 2020 evaluation METR Time Horizon 1.1 dataset

About this Dataset

In mid-2020, an AI agent built on an early GPT-3-class model could autonomously complete tasks requiring roughly 9 seconds of equivalent human expert effort at the 50% success rate threshold. By April 2026, an early preview of Claude Mythos reached a 50% task horizon of approximately 17.4 hours on METR's Time Horizon 1.1 (TH1.1) benchmark — provisionally, since that figure sits above the roughly 16-hour range where METR's current task suite can produce a reliable estimate. That progression — from 9 seconds to 62,687 seconds — spans nearly four orders of magnitude (roughly 7,000×) in under six years and represents the most systematically measured trajectory of AI agentic capability currently available in published research.

The metric behind this chart is METR's task time horizon, introduced in the March 2025 paper "Measuring AI Ability to Complete Long Tasks" (Kwa et al., arXiv:2503.14499) and since re-baselined under the Time Horizon 1.1 methodology. The 50% task time horizon is defined as the human expert completion time of the task at which a frontier agent succeeds approximately half the time when working entirely autonomously. "Human expert completion time" is the critical unit: it measures the difficulty of the task as a proxy, not how long the AI takes to execute. Every point on this page, from GPT-4 in March 2023 through Claude Mythos Preview in April 2026, is now drawn from the same TH1.1 dataset, resolving a partial methodological mismatch that existed in earlier versions of this chart, when historical points came from the original HCAST-only evaluation and newer points came from TH1.1.

METR's own curve fit puts the doubling time for the 50% task time horizon at roughly 6.2 months across the full 2020–2026 history, accelerating to roughly 4.2 months when the fit is restricted to 2023 onward — a rate that, if sustained, would imply day-length autonomous task capability within the next one to two years. Whether that rate is sustained remains empirically open, and METR's own task suite already struggles to measure reliably above roughly 16 hours.

The growth pattern is most clearly visible on the logarithmic scale used in the chart above. On a log axis, each doubling of the task horizon appears as an equal vertical increment. The trajectory from GPT-4 (approximately 4 minutes, March 2023) to GPT-4o (approximately 7 minutes, May 2024) represents a modest single-year gain; from GPT-4o to Claude 3.5 Sonnet (approximately 21 minutes, October 2024) is roughly one and a half additional doublings across five months. The frontier has kept moving since: Claude Opus 4.6 reached roughly 12 hours (11h 59m) by February 2026 — the same week OpenAI's GPT-5.3-Codex reached roughly 5h 50m, illustrating that different labs' frontier releases in the same month can sit far apart on this metric. An early preview of Claude Mythos then reached a provisional ~17.4 hours by April 2026, the highest figure recorded and the first point to exceed METR's stated reliable-measurement ceiling. As of September 2026, METR had not yet published time horizons for several newer releases, including Claude Opus 4.7, GPT-5.5 and Grok 4.3, so Claude Mythos Preview remains the latest point in the dataset.

Two scope limitations are essential context for professional use of this data. First, the underlying task suite (HCAST, extended under Time Horizon 1.1) is predominantly a software engineering benchmark. Most tasks involve Python scripting, shell automation, data pipelines, repository navigation, and related programming-adjacent work in a sandboxed Linux environment. The benchmark does not systematically cover the sustained natural-language reasoning, interpersonal coordination, and domain-specific judgment that characterise many professional workflows. A multi-hour task horizon on this benchmark does not imply equivalent autonomous capability across general office work. Second, point estimates carry approximately ±30–50% uncertainty as ratios, and the most recent point is explicitly flagged by METR as provisional: its own published estimate for Claude Mythos Preview is "at least 16 hours," with a 95% confidence interval spanning 8.5 to 55 hours, considerably wider than the single point estimate plotted on this chart. In March 2026, METR also corrected a regularisation error in its estimation pipeline, which revised several point estimates — including Claude Opus 4.6's — materially downward from what had previously been reported; the figures on this page reflect that correction.

The mid-2020 data point deserves a separate note: it is METR's earliest Time Horizon 1.1 baseline, applied retrospectively to an early GPT-3-class model, not a contemporaneous evaluation. Systematic task-horizon methodology did not exist in 2020; the roughly 9-second estimate is derived by back-fitting the observed trend and applying it to documented early agent performance. It should be treated as an indicative anchor rather than a precision measurement.

For policy researchers and investors, the practical signal in this dataset is primarily about pace of capability development rather than deployment readiness. Benchmark performance in a controlled sandbox environment and autonomous operation in real enterprise workflows involve meaningfully different conditions: live enterprise settings typically include authentication and access management, embedded human approval gates, integration with legacy systems not designed for agent access, and accountability structures where errors carry organisational consequences. The gap between benchmark capability and deployable autonomy is not constant, and measuring it requires empirical evidence from real deployment contexts — which the HCAST/TH1.1 benchmark alone does not provide.

Key methodological notes for quantitative use of this dataset:

  • Task time unit: "Human expert completion time" is a difficulty proxy rated by annotators, not AI execution time. The two can differ substantially.
  • Logistic curve fitting: The 50% horizon is a model-derived estimate, not a directly observed value. Point estimates carry ±30–50% uncertainty as ratios.
  • Benchmark scope: HCAST and TH1.1 are software-engineering-heavy. Performance on general professional tasks may differ substantially.
  • Single consistent methodology: Every point on this page is drawn from METR's Time Horizon 1.1 dataset, applied consistently from GPT-4 (2023) through Claude Mythos Preview (2026), replacing the mixed HCAST/TH1.1 sourcing used in earlier versions of this chart.
  • Measurement ceiling: METR's current task suite reliably measures horizons up to roughly 16 hours. The Claude Mythos Preview point (~17.4 hours) exceeds that ceiling and is provisional; METR's own published range for it is 8.5 hours to 55 hours (95% confidence interval).
  • Regularisation correction: METR corrected an error in its estimation pipeline in March 2026, revising some point estimates — including Claude Opus 4.6's — downward from previously reported levels.
  • Retrospective baseline: The mid-2020 estimate is a back-fitted retrospective, not a contemporaneous evaluation.
  • Trend extrapolation: The observed doubling rate is a historical pattern in seventeen data points. It carries no mechanistic guarantee of continuation, acceleration, or saturation.

Frequently Asked Questions

The 50% task time horizon is the length of task at which a frontier AI agent succeeds approximately half the time when operating autonomously without human guidance. Task length is measured in human expert completion time — the estimated time a skilled human professional would require to perform the same task from scratch — not in wall-clock AI execution time. That distinction matters: a task rated at 40 minutes of human expert time might take an AI agent hours, or might be completed much faster through parallelism; the metric captures task complexity rather than AI speed. METR derives this estimate by fitting a logistic curve to a large set of tasks, each pre-rated by human annotators for complexity, then running AI agents on those tasks in a sandboxed environment. The 50% success rate threshold is chosen because it sits in the most informative region of the logistic curve — where task difficulty and agent capability interact most visibly. The resulting metric compresses the agent's capability distribution to a single interpretable number: the task difficulty, in human-time units, where the agent is about as likely to succeed as to fail.

The 50% task time horizon has grown from approximately 9 seconds in mid-2020 to 62,687 seconds (about 17.4 hours) by April 2026 — a factor of roughly 7,000 in under six years. Plotting this trajectory on a linear axis would make the early data points (an early GPT-3-class model at 9 seconds, GPT-4 at roughly 4 minutes) visually indistinguishable from zero, while compressing all the interesting variation into a near-vertical spike at the right edge. A logarithmic scale allows every doubling of the horizon to appear as an equal vertical step, which matches the underlying pattern in the data: METR's own curve fit puts the doubling time at roughly 6.2 months across the full 2020–2026 history, accelerating to roughly 4.2 months when the fit is restricted to 2023 onward. On a log scale, a straight trend line indicates consistent exponential growth; deviations from linearity reveal acceleration or deceleration. The chart therefore does not exaggerate the trend — it is the scale that makes the empirical regularity visible without distortion.

HCAST (Human-Comparable Agentic Software Tasks) is a benchmark suite developed by METR that consists of hundreds of real-world software engineering and technical tasks sourced from online task platforms, professional workflows, and internal test development. Tasks span Python scripting, shell automation, repository navigation, data analysis pipelines, web scraping, bug reproduction, and similar programming-adjacent work. Agents are evaluated in a sandboxed Linux environment with access to standard tools, internet-connected resources where tasks require them, and no human interaction during the task. The benchmark is specifically designed so that each task has a verifiable, objective completion criterion — allowing binary scoring without subjective judgment. The critical scope limitation is that HCAST is predominantly a software engineering benchmark. The majority of tasks are solvable by someone with programming competence; general professional tasks requiring sustained natural-language reasoning, interpersonal coordination, visual judgment, or domain expertise outside software are largely absent from the current suite. METR's Time Horizon 1.1 update, published January 2026, expanded the task set to 228 tasks, including 31 tasks estimated to take human experts 8 or more hours — up from 14 such tasks in the prior version — which widened the measurable range without substantially broadening the task type distribution. Inferences about agent capability in non-technical workplace contexts should be made cautiously from this data.

The observed doubling time — roughly 6.2 months across the full 2020–2026 history, accelerating to roughly 4.2 months (with a 95% range of about 3.4 to 5.2 months) since 2023 on METR's own curve fit — is an empirical pattern in a historical dataset of seventeen data points, not a physical law or a guaranteed trajectory. Several factors could cause the trend to slow: benchmark saturation is possible if current task sets become fully solved before longer tasks are added; the tasks that remain hardest may require qualitatively different capabilities not currently improving at the same rate; and real-world deployment constraints — authentication, approval gates, organisational context — not present in HCAST may limit practical capability gains even as benchmark scores continue to rise. The trend could also accelerate if architectural changes, improved scaffolding, or expanded tool access produce larger-than-typical capability jumps in individual model releases. METR's own published commentary frames the trend descriptively rather than predictively, and its most recent point — Claude Mythos Preview at a provisional ~17.4 hours — already sits above the roughly 16-hour range where METR says its current task suite can produce a reliable estimate. No published mechanistic model explains why the doubling rate should be stable or should change at any particular threshold. Any forward projection from this chart carries substantial uncertainty and should be treated as illustrative rather than predictive.

The benchmark measures performance in a controlled, sandboxed environment on software-oriented tasks with objective completion criteria. Autonomous task completion in real enterprise workflows typically introduces several layers of complexity absent from HCAST: authentication and access management across multiple systems; human approval gates embedded in procurement, legal, and compliance workflows; integration with legacy software not designed for API or agent access; ambiguous or evolving task specifications that require iterative human clarification; and accountability structures where errors have real organisational consequences. A model capable of completing a benchmark task measured at roughly 12 hours (Claude Opus 4.6, February 2026) — or provisionally beyond 16 hours (Claude Mythos Preview, April 2026) — autonomously may still require substantial human oversight infrastructure when deployed on tasks of equivalent nominal duration in a live enterprise setting. The benchmark is most directly informative for organisations building agentic pipelines in software development, data engineering, or technical operations — where HCAST's task composition more closely mirrors actual work. For policy researchers and investors, the metric provides a quantitative proxy for the pace of capability development; it does not directly translate to workforce substitution estimates or deployment-readiness conclusions without additional empirical evidence from real deployment contexts.

Reliability varies across the dataset. The mid-2020 data point is METR's earliest Time Horizon 1.1 baseline, applied retrospectively to an early GPT-3-class model; it was not a contemporaneous evaluation and carries higher uncertainty than the later points. Every point on this page — from GPT-4 in March 2023 through Claude Mythos Preview in April 2026 — is now drawn from METR's Time Horizon 1.1 (TH1.1) dataset, the single, currently canonical benchmark version METR applies consistently across the full 2020–2026 history. That is an improvement on the methodology used in earlier versions of this dataset, where historical points came from the original HCAST-only evaluation described in the March 2025 paper (arXiv:2503.14499) and newer points came from TH1.1, creating a partial mismatch; METR has since re-evaluated the historical models under TH1.1, and the point estimates on this page reflect that re-evaluation. In one documented instance, METR corrected a regularisation error in its estimation pipeline in March 2026, which revised several point estimates, including Claude Opus 4.6's, materially downward. Point estimates generally carry roughly ±30–50% uncertainty expressed as a ratio; a stated horizon of 40 minutes plausibly covers a range from approximately 20 minutes to 60 minutes. The most recent point, Claude Mythos Preview, sits above the roughly 16-hour range where METR's task suite has enough long-duration tasks to produce a reliable estimate; METR's own published figure for that evaluation is 'at least 16 hours' with a 95% confidence interval of 8.5 to 55 hours, wider than the point estimate used on this chart implies. For quantitative modelling applications, the confidence interval data — available via Epoch AI's benchmark tracking page and METR's own published notes — should be incorporated rather than relying solely on point estimates.