Skip to content

Agent push calculator

How many pushes will your agents waste?

When many agents push to one branch, a Git host that only accepts a push made on top of the newest main lets one in and turns the others away. Each agent that is turned away has to fetch, rebase and push again, and often wait for CI to pass again too. Describe your agents below and see what that costs them. It all runs in your browser: nothing you enter leaves this page.

Your agents

How they finish their work
seconds

3 seconds is close to one round in our GitHub.com test below.

For example a required check on an up-to-date branch: a rebased change is a new change, so its earlier CI result no longer counts.
minutes
USD

Default $0.006: GitHub Linux 2-core list price, Jan 2026.

How many times a day every agent finishes a change and pushes it to main.

Each run

45rejected pushes

10 agents each put one change on main at the same moment.

Extra push rounds
9
Pushes the unluckiest agent made beyond its first.
Time until every change is on main
1 h 13 min
Your agents spent 6 h 2 min in all on pushing again and re-running CI.
CI minutes re-run
7,200 a day
216,000 a month (30 days).
What they cost
$1,296.00 a month
$43.20 a day at $0.006 a minute.

At this pace one run takes 1 h 13 min, so 20 runs do not fit in a day: they would overlap and lose even more pushes, so the CI figures above are lower than they would really be.

rejected pushchange on main8 of 10 agents, in the order their change reached main.

How this is worked out

This is an estimate from a simple model, not a measurement.

  • One rule, the same on any Git host that only accepts a push made on top of the newest main: when several agents push at the same moment, one change lands and every other push is rejected. Each rejected agent fetches main, rebases its change and pushes again.
  • All at the same moment: the rounds have n, n − 1, …, 1 agents pushing, so the rejected pushes add up to (n − 1) + (n − 2) + … + 1 = n(n − 1) / 2. For 10 agents: 10 × 9 / 2 = 45.
  • Spread out: each agent finishes at a random moment within the minutes you set (drawn the same way every time, so the same inputs give the same answer). A push reaches the host one round after the agent fetched, and lands only when no other change landed in between. The numbers are the average of 100 runs; the diagram shows the run closest to that average.
  • Time: a first push takes one round. Each retry takes one round, plus one CI run when CI must pass again after a rebase. The agents’ time spent pushing again is the rejected pushes × one retry.
  • CI minutes re-run = rejected pushes × CI minutes per run, times the runs per day; a month is 30 days. Cost = those minutes × the price per minute.
  • Not counted: the one CI run every change needs anyway, the time agents spend on the work itself, waiting for a free runner, flaky tests, and changes that clash and need someone to fix them.