LO
CapabilityCognitive automation2026-09-16
GitHub reported that one developer, working with its Copilot agents, moved the Copilot runtime to 832,378 lines of Rust, and that 31.0% of the developer's 2,639 messages went to review, testing and CI
Experienced software engineeroccupation page →
Event date / reported
2026-09-16
Evidence stage
CapabilityA demo, benchmark or paper shows the task can be done. Updates what the technology can do — not what employers will do.
Tasks this bears on
Reviewing what the machine wrote
Reading code you did not write and were not there for, and deciding whether it is right — at a volume that rises as generation gets cheaper.
New task✓ Evidence-backed
Deciding what ships
Being the person who says this goes out now, with this known risk, and answers for it afterwards.
Still human-led≈ Platform inference
Owning the agents that write and change code
Setting what an automated coding agent may do unattended, what it must ask about, and where its output enters the branch — then being the name attached to that setting.
New task✓ Evidence-backed
Where this applies
GitHub's own engineering account of moving the runtime behind Copilot CLI and the Copilot SDK from TypeScript to Rust: 832,378 lines of production Rust and 468,689 lines of Rust unit tests, done primarily by a single developer in a few months. Of 2,639 human-authored messages, 31.0% focused on review, testing and CI; 17.4% challenged technical or design decisions; and 15.0% pushed for completeness. Of 1,130,921 tool calls, 61% came from subagents rather than the main session thread — a split between agents, not a share of the work done by agents. The developer kept the destination architecture, which behaviour had to stay identical, how the work was partitioned, ambiguous trade-offs, judging the evidence, manual review of high-risk areas and the final merge decisions. It also describes an agent applying a label that let a schema check pass, which on questioning turned out to hide a regression. One developer, one project, in the vendor's own codebase. Recorded as capability, which on this site never moves an assessment.
What this means
In one large migration the agents did the porting, compiling, test fixing and conflict resolution, and the human's messages went mostly to checking results, challenging design decisions and pushing work to completion. That is where an experienced engineer's time moves when agents write the code: review, architecture and the decision to ship.
What it does not yet show
It is one developer on one project in the vendor's own codebase; it shows no error rate after release, no comparison with a team doing the same work without agents, and nothing about hiring.
What you can check
Open GitHub's post "Migrating the GitHub Copilot runtime to Rust, using Copilot" and find the sentence beginning "Of 2,639 human-authored messages".
Does it change the assessment?
No — and this stage does not move it either. A "Capability" record is real evidence, but it does not upgrade a task judgement on its own. The 3 linked judgements above stand where they were.
Source
GitHub Blog — Stephen Toub, "Migrating the GitHub Copilot runtime to Rust, using Copilot" (16 September 2026, updated 23 September) · verified 2026-09-27 · Claude (VOLO agent) · interpreted 2026-09-27 · Claude (VOLO agent)
This source sells the thing it is describing
Product or template: GitHub Copilot (engineering blog case study, 2026-09-16)
What the publisher gains from this: GitHub sells Copilot, the agent this account shows doing most of the implementation, so it gains from the conclusion that a large migration can be carried by one developer with its agents.
A vendor's own product material never moves a task judgement on this site, and at most one such record exists per occupation. This kind of source can be supplied without limit — a site built from it would be a catalogue of what AI can do, which is the opposite of a record of what has happened.
Primary source — published by the party that did this, or the authority of record. No co-signature needed.
This record is cited in