Equation 1 · From Origins to Frontier: A History of Claude Code and Agentic Development Tools
What does this equation mean?
Read the formula alongside the article passage below. Each part has a deeper page with its role in the equation, the supporting passage and nearby citations.
This equation gives an approximation: it relates the quantities while allowing an approximation. Read the equation part by part below; each part has a contextual explanation and a link to its mathematical background.
Read it piece by piece
Symbol T_50
the length of task, measured in human-hours, that a frontier agent could complete autonomously with 50% reliability at time t.
Symbol T_0
is one of the signed contributions combined to compute the quantity on the left.
Symbol t_0
is one of the signed contributions combined to compute the quantity on the left.
Symbol τ
τ is one of the signed contributions combined to compute the quantity on the left.
=
The expressions on both sides represent the same quantity under the stated assumptions.
See an illustrated explanation →subtraction
Subtract the following term or group from the preceding one. A leading minus marks a negative quantity.
subscript
The lower label selects a particular version, component, or indexed member of the quantity. For example, x₀ and xₜ can be values at different positions.
superscript
A raised number can be a power. When it is a label or bound, it selects a case or the upper limit of a sum; the formula’s structure distinguishes these uses.
See an illustrated explanation →How to interpret it
Its accuracy depends on the assumptions and range of use described in the article. Read it with the definitions, units, and assumptions supplied by the article.
What the article says around this equation
A second, independently run measurement effort took a different approach: instead of asking whether an agent could solve one fixed set of tasks, it asked how long a task an agent could complete autonomously with 50% reliability, using human professional completion time as the unit. METR’s March 2025 study, compiled from 170 tasks and more than 800 human timing baselines across software engineering, cybersecurity and general reasoning work, reported that this “50%-task-completion time horizon” for frontier agents had been doubling approximately every seven months for six years running, and that the finding was robust to an order-of-magnitude error in the underlying measurements, which would…
Read the full surrounding passage
A second, independently run measurement effort took a different approach: instead of asking whether an agent could solve one fixed set of tasks, it asked how long a task an agent could complete autonomously with 50% reliability, using human professional completion time as the unit. METR’s March 2025 study, compiled from 170 tasks and more than 800 human timing baselines across software engineering, cybersecurity and general reasoning work, reported that this “50%-task-completion time horizon” for frontier agents had been doubling approximately every seven months for six years running, and that the finding was robust to an order-of-magnitude error in the underlying measurements, which would only shift the projected timeline by around two years [ 14 ] . Writing the trend as a simple exponential makes its shape explicit: . where is the length of task, measured in human-hours, that a frontier agent could complete autonomously with 50% reliability at time t . This is an empirical regression over six years of a specific evaluation methodology, not a law of nature, and METR’s own reporting is explicit that the trend could bend in either direction; it is included here because it is the clearest available answer to “how would you know if agentic coding tools were actually getting more autonomous,” as distinct from “how would you know if a vendor said so.”
Sources cited in the surrounding passage
These citations give research context. Read each source to check which claims it supports.
Return to From Origins to Frontier: A History of Claude Code and Agentic Development Tools