Microsoft's Copilot Cowork team goes empty-repo to worldwide GA in 4.5 months with agents writing most of the code, then ports the live runtime from Python to Rust
A small Microsoft team started Copilot Cowork from an empty repo on 13 January 2026 and reached worldwide GA on 16 June (~4.5 months), with agents writing most of the code behind markdown specs, narrow parallel agents, competing review bots, and repo-stored rules. Merged PRs rose from 257 in January to 2,754 in May; on 21 October nine engineers merged 1,211 PRs into the backend main branch in a day. After GA they moved the live runtime from Python to Rust (first production turns 24 September, Python deleted 9 October ~8,000 files / 4.9M lines including tests and generated code, last cluster 10 October), using ~430 Python-generated fixtures as the Rust acceptance suite. Session first-token p50 fell from 7.9s to 2.7s in a late-September cluster comparison.
The numbers (as reported)
| Empty repo to worldwide GA | 13 Jan to 16 Jun 2026 (~4.5 months) |
|---|---|
| Merged PRs per month | 257 in January → 2,754 in May; busiest pre-GA week 783 |
| Peak day | 1,211 PRs merged by nine engineers on 21 Oct 2026 |
| Factory week | 4,581 PRs merged week of 12 Oct (~650/day) |
| Python deleted at cutover | ~8,000 files and 4.9 million lines (incl. tests and generated code) on 9 Oct |
| First-token latency (same 12h window) | Python p50 7.9s / p90 14.5s → Rust p50 2.7s / p90 6.2s |
| Parity fixtures | ~430 fixtures generated from live Python behaviour |
| Test-speed harness | ~300 merged PRs; touched tests ~17,700s → ~1,700s CI time |
Facts
- Company / subject
- Microsoft (Copilot Cowork)
- Tools
- Unstated
- Codebase
- mixed
- Work type
- New product
- Stack
- Python, Rust, Microsoft 365, containers
- Published
- 2026-11-02
- Last checked
- 2026-11-05
What the source claims Practitioner (own blog/paper)
Claimed by the builder, writing about their own work. Not checked independently.
- Worldwide GA about four and a half months after the first commit ~4.5 months
“We reached worldwide general availability on June 16, about four and a half months after the first commit”
- Time to first token on the first turn of a session dropped a lot after the Rust cutover p50 7.9s → 2.7s
“Time to first token on the first turn of a session dropped a lot.”
- Touched test files cut CI time from roughly 17,700 seconds to about 1,700 across ~300 harness PRs ~17,700s → ~1,700s
“Across them, the touched test files went from roughly 17,700 seconds of CI time to about 1,700.”
Caveats
Self-reported Microsoft eng post. The specific coding-agent product is not named (only “agents”). Latency gain partly attributed to moving the agent loop out of the container, not Rust alone. No cost-per-turn claim.
More stories by tool: Unstated
Related topics: New products built with agents