Estimating with an agent

How long will a build take when an agent does the typing?

Type how many lines the change will touch. You get a range from 66 real merged branches, not a point guess. The assumptions are listed under the answer, and the table behind it is below.

A rough size is fine. "1,200" and "1.2k" both work.

16 minutes
Typical
Half of the 27 comparable branches finished faster.
55 minutes
Plan for
The number to give someone who is waiting. You blow past it one time in five.
83 minutes
Bad day
One time in ten it takes longer than this.

Class used: 100 to 999 lines. Review and shipping are on top: reading the diff, running it, checking the deployed result. That time is not in this table.

The table behind it

Every branch merged since 2026-03-10 on one machine: first commit on the branch to the merge, in hours of wall clock.

Branch sizeCountTypicalPlan forBad day
Under 100 lines28under 1 minute5 minutes27 minutes
100 to 999 lines2716 minutes55 minutes83 minutes
1,000 lines or more1170 minutes3.3 hours7.5 hours

Assumptions, stated

  • The sample is 66 branches, 44,778 changed lines, 5 repositories, one builder. It is mine, not yours.
  • Only branches that merged with a merge commit are timed. Squash merges and direct commits leave nothing to measure, so every figure is a floor.
  • The time includes waiting. A branch that sat for days counts as days, which is why the bad day column is long.
  • It measures the build, not the decision before it and not the review after it.
  • The script that prints this table reads only git history, so you can run it on your own clones: scripts/reference-class.py in this site's repository.

The reasoning, and the five rules these numbers feed: How to estimate a build when an agent does the typing.

How this was measured. Counted on 2026-11-17 with scripts/reference-class.py. Nothing you type here leaves your browser.