Nine engineers, 1,211 PRs in a day: Lessons from building Copilot Cowork
Comments on “Nine engineers, 1,211 PRs in a day: Lessons from building Copilot Cowork”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Microsoft's Command Line blog describes how nine engineers took Copilot Cowork from an empty repo on January 13 to general availability on June 16, with agents writing most of the code, then replaced the live Python runtime with Rust by October 10. It reports 1,211 merged PRs in one day and median time to first token falling from 7.9 s to 2.7 s, partly because the agent loop also moved. Practices include specs first, replayable fixtures, and checks that must fail on purpose. All figures are self-reported.
Why it ranked
No. 7 of 137 with a score of 0.73. The panel rated it highest on new information (0.88) and reader interest (0.87), lowest on significance (0.65). Placed No. 7, No. 8 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- Detailed engineering writeup of building an agentic product with concrete process and migration data, though it is partly a vendor promotional story and some metrics are self-reported.
- AI judgeJudge 3gpt-5.6-luna
- A detailed first-person engineering account with concrete architecture, review controls, automation metrics, Rust migration data, fixtures, and failure cases. It is highly actionable, though tied to one large product and includes modest launch framing.
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.73total under rubric v2.3
- Significance0.65
- Reader interest0.87
- Audience breadth0.72
- Practical relevance0.86
- Substantiated0.81
- Technical depth0.85
- New information0.88
- Counts against: Promotional0.21
- Counts against: Overclaim0.19
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.72 | 0.45 | 0.78 | 0.65 | 0.33 | +0.24 | +0.156 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.82 | 0.82 | 0.97 | 0.87 | 0.15 | +0.26 | +0.226 |
| Audience breadthHow many people who build technology does it concern? | 0.68 | 0.70 | 0.78 | 0.72 | 0.10 | +0.13 | +0.093 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.93 | 0.75 | 0.91 | 0.86 | 0.18 | +0.22 | +0.190 |
| 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.94 | 0.60 | 0.89 | 0.81 | 0.34 | +0.05 | +0.041 |
| Technical depthHow technically substantive is it? | 0.96 | 0.70 | 0.90 | 0.85 | 0.26 | +0.05 | +0.043 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.85 | 0.85 | 0.94 | 0.88 | 0.09 | +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.09 | 0.35 | 0.18 | 0.21 | 0.26 | −0.19 | −0.039 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.20 | 0.30 | 0.08 | 0.19 | 0.22 | −0.11 | −0.021 |
| Sum of contributions | +0.732 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.732 | ||||||
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-04/7/"><img src="https://rubric.hrih.si/badge/2026-11-04/7.svg" alt="Ranked #7 on Rubric, 4 Nov 2026" width="231" height="28"></a>Claim check
Claim check: 4 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenNumber
On October 21, nine engineers merged 1,211 pull requests into the main branch of the Copilot Cowork backend.
The article gives no link or citation for it.
The article says “On October 21, nine engineers merged 1,211 pull requests into the main branch of the Copilot Cowork backend”
The source says No source to compare with.
No source givenDate
Copilot Cowork went from an empty repo to worldwide general availability on June 16, about four and a half months after the first commit on January 13, with several models and 16 plugins.
The article gives no link or citation for it.
The article says “We reached worldwide general availability on June 16, about four and a half months after the first commit, with several models and 16 plugins”
The source says No source to compare with.
No source givenNumber
Merged PRs per month grew from 257 in January to 2,754 in May, and the busiest week before GA had 783.
The article gives no link or citation for it.
The article says “Merged PRs per month went from 257 in January to 2,754 in May. Our busiest week before GA had 783”
The source says No source to compare with.
No source givenDate
Copilot Cowork launched to its first enterprise customers in the Frontier program on March 30.
The article gives no link or citation for it.
The article says “We launched Copilot Cowork to our first enterprise customers in the Frontier program on March 30”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 1 pts, not on front page
Recorded for context only, checked 4 Nov 2026, 05:47 UTC. It played no part in the ranking.