The CI bill in the agent era: what GitHub’s Actions pricing reset tells engineering teams

5-minute read · Updated 28 October 2026

• Cheaper hosted runners. On January 1, 2026, GitHub cut prices for its hosted runners by up to 39%, depending on machine size.
• A paused fee. A $0.002-per-minute charge on self-hosted runners, planned for March 1, was postponed for re-evaluation. No new date has been set.
• Public stays free. Public projects used 11.5 billion Actions minutes in 2025, worth about $184 million by GitHub’s count.
• Agents raise the stakes. Agents that iterate through CI, and AI code review that runs on Actions minutes, push usage up.

GitHub described the January change as a cut of roughly 40% across runner sizes, combined with a new cloud platform charge that is already included in the lower per-minute price. Smaller runners saw smaller reductions and larger ones bigger reductions.

The same announcement said the platform charge would also apply to self-hosted runners from March 1, at $0.002 per minute, and that self-hosted minutes would start counting against plan quotas. Teams that had moved to their own machines precisely to avoid per-minute pricing pushed back hard. GitHub postponed the change to re-evaluate its approach and has not announced a new date. It has not withdrawn the idea either.

At the announced rate, a million self-hosted minutes a month would add $2,000, and five million would add $10,000. That is small next to the cost of the machines themselves. But it is a new line for teams whose whole reason for self-hosting was a CI bill that did not grow with every run.

The cheapest CI minute is the one an agent never needed to run.

• Agents iterate through the pipeline. Fixing a failing build often means pushing and running CI again, sometimes many times.
• Parallel agents multiply runs. Several agents on several branches each trigger their own pipelines.
• AI review runs on CI. GitHub says Copilot code review consumes Actions minutes at standard rates.
• Failed runs ship nothing. Every red build is a cost without a result, and agents produce more of them on the way to green.

1. 1

   Measure minutes per merged change

   Total minutes say little. Minutes per change that reached production show whether CI is getting more efficient.
2. 2

   Separate failed runs

   Track the share of minutes spent on runs that failed or belonged to changes that were never merged.
3. 3

   Compare hosting on total cost

   Self-hosted runners are free of GitHub minute charges today, but machines and upkeep are not. Re-check the maths when the fee returns.
4. 4

   Cancel superseded runs

   Concurrency limits and cancelling in-progress runs on new pushes are cheap wins when agents push often.

CI is one link in the chain Nythrex follows from AI session to production. Pipeline runs are attached to the change they verified, failed runs stay visible, and CI within included minutes is labelled as an estimate from the price list rather than shown as free.

How the chain works

• GitHub — Pricing changes for GitHub Actions (2026)
• GitHub Changelog — Simpler pricing and a better experience for GitHub Actions (December 2025)
• SAMexpert — GitHub Actions pricing: price cuts, backlash and a rapid retreat
• GitHub Blog — Copilot code review and Actions minutes (April 2026)