Our Coding Agents Outgrew GitHub's Runners
Comments on “Our Coding Agents Outgrew GitHub's Runners”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
A Bruno J. post describes how a company's coding agents pushed weekly pull requests from 42–75 in June to 694 in late October, and how it moved most CI off GitHub's runners to a €99-a-month dedicated server. GARM gives each job a fresh Incus VM. GitHub-billed minutes fell from 19,359 to 611 in three weeks. Costs include slow busy afternoons, a single point of failure, and a possible GitHub self-hosted fee. The figures are self-reported, and the link to the Opus 5.5 release is the author's inference.
Why it ranked
No. 11 of 107 with a score of 0.65. The panel rated it highest on new information (0.88) and substantiated (0.84), lowest on significance (0.49). Placed No. 11, No. 20 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- Detailed engineering write-up on moving CI from GitHub runners to a self-hosted VM-per-job setup driven by GARM, with concrete metrics and costs; practical for builders, though narrow in scope and self-reported.
- AI judgeJudge 3gpt-5.6-luna
- A detailed, data-rich engineering account of scaling CI for agent-generated pull requests, including cost, queueing, isolation, implementation, performance, and failure modes. It is highly actionable, though primarily relevant to teams with unusually high CI volume.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.65total under rubric v2.3
- Significance0.49
- Reader interest0.76
- Audience breadth0.52
- Practical relevance0.78
- Substantiated0.84
- Technical depth0.79
- New information0.88
- Counts against: Promotional0.05
- Counts against: Overclaim0.18
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.49 | 0.35 | 0.62 | 0.49 | 0.27 | +0.24 | +0.117 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.72 | 0.70 | 0.86 | 0.76 | 0.16 | +0.26 | +0.198 |
| Audience breadthHow many people who build technology does it concern? | 0.46 | 0.55 | 0.55 | 0.52 | 0.09 | +0.13 | +0.067 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.82 | 0.70 | 0.82 | 0.78 | 0.12 | +0.22 | +0.171 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.90 | 0.70 | 0.91 | 0.84 | 0.21 | +0.05 | +0.042 |
| Technical depthHow technically substantive is it? | 0.89 | 0.70 | 0.78 | 0.79 | 0.19 | +0.05 | +0.040 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.87 | 0.80 | 0.96 | 0.88 | 0.16 | +0.05 | +0.044 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.05 | 0.05 | 0.06 | 0.05 | 0.01 | −0.19 | −0.010 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.27 | 0.20 | 0.08 | 0.18 | 0.19 | −0.11 | −0.020 |
| Sum of contributions | +0.648 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.648 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-03/11/"><img src="https://rubric.hrih.si/badge/2026-11-03/11.svg" alt="Ranked #11 on Rubric, 3 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 4 matches source · 3 no source given · 1 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Couldn’t checkDate
Anthropic released Claude Opus 5.5 on 22 September.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “on 22 September, Anthropic released Claude Opus 5.5”
The source says No passage could be compared.
Source cited by the article: anthropic.com/claude-opus-5-5
Matches sourceNumber
GitHub's standard runner for private repositories has 2 CPUs.
The cited source says the same thing.
The article says “GitHub's standard runner for private repositories has 2 CPUs”
The source says “Linux | 2 | 8 GB | 14 GB | x64 | ubuntu-latest , ubuntu-24.04 , ubuntu-22.04 , ubuntu-26.04”
Source cited by the article: docs.github.com/en/actions/reference/runners/github-hosted-runners
Matches sourceNumber
The GitHub Team plan runs at most 60 jobs at once.
The cited source says the same thing.
The article says “The Team plan runs at most 60 jobs at once”
The source says “Standard GitHub-hosted runner | Team | 60 | 5 | Not applicable”
Source cited by the article: docs.github.com/en/actions/reference/limits
Matches sourceDate
In December 2025 GitHub announced a $0.002 per minute charge for self-hosted runners, then put it on hold.
The cited source says the same thing.
The article says “In December 2025 GitHub announced a $0.002 per minute charge for self-hosted runners, then put it on hold”
The source says “We’re postponing the announced billing change for self-hosted GitHub Actions to take time to re-evaluate our approach”
Source cited by the article: github.blog/changelog/2025-12-16-coming-soon-simpler-pricing-and-a-better-experience-for-github-actions
Matches sourceNumber
GitHub's own tool for autoscaling runners, actions-runner-controller, is a Kubernetes operator.
The cited source says the same thing.
The article says “GitHub's own tool for autoscaling runners is actions-runner-controller, which is a Kubernetes operator”
The source says “Actions Runner Controller (ARC) is a Kubernetes operator that orchestrates and scales self-hosted runners for GitHub Actions”
Source cited by the article: docs.github.com/en/actions/concepts/runners/actions-runner-controller
No source givenNumber
The company opened 694 pull requests in the last week of October, versus 42 to 75 a week in June.
The article gives no link or citation for it.
The article says “In the last week of October, our company opened 694 pull requests. In June it was between 42 and 75 a week”
The source says No source to compare with.
No source givenNumber
GitHub-billed runner minutes fell from 19,359 in the week of 5 October to 611 in the week of 26 October after the move to the rented server.
The article gives no link or citation for it.
The article says “26 October 694 611”
The source says No source to compare with.
No source givenCausal conclusion
The Opus 5.5 release caused the jump in pull requests, from 244 to 458 in one week.
The article gives no link or citation for it.
The article says “That week we opened 458 pull requests, up from 244 the week before”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 2 pts, not on front page
Recorded for context only, checked 3 Nov 2026, 05:47 UTC. It played no part in the ranking.