Microsoft's agents ported Copilot's runtime to Rust for $120K

Share
Microsoft's agents ported Copilot's runtime to Rust for $120K

GitHub rewrote the engine behind Copilot from TypeScript to Rust, with AI agents doing most of the typing — and put a receipt on the whole project.

GitHub says it ported the entire Copilot agent runtime to Rust, with agents writing the bulk of the code, for roughly $120,000 in tokens. The project — described by GitHub engineer Stephen Toub — started from a scoping estimate of about 130,000 lines of TypeScript and ended with more than 800,000 lines of production Rust, after roughly 430,000 lines of TypeScript passed through the port. Work landed as 128 pull requests merged incrementally into main rather than one cutover, spanning about 14.5 weeks and over 135 releases. The token bill was 136.3 billion tokens, most of it cached input reads; The Register puts the human cost at about three weeks of a developer's time, with a single developer carrying most of the work alongside a team that kept shipping features.

The performance numbers are the reason this is a story and not a blog post. On a benchmark of 1,000 one-turn session lifecycles sharing one client across 100 concurrent pipelines, the old TypeScript runtime managed 7.55 per second; Rust running in-process hit 120 per second, a 15.9x gain on that specific workload — Rust out-of-process landed at 57.45. Memory moved further: a ten-client batch peaked 1,383 MB above baseline under TypeScript and 126 MB in-process under Rust, a 91 percent cut, because the work no longer needs to spawn external background processes. GitHub's own framing is careful, and correct — the runtime is not universally 15.9x faster. But multi-session hosts are exactly the case server operators pay for.

What agents actually did is the more interesting finding. Across tool telemetry, sessions spent about ten times more effort gathering evidence than changing code — reading files, searching the repo, running diagnostics — which inverts the popular image of AI spraying code. The model-orchestration port ran a 42-hour wall-clock session that spawned 126 subagents, 22 working at once. One session used an orchestration skill to find every other active session and message the ones whose missions overlapped. Different jobs went to different models by strength: GPT-5.6 Sol and Claude Opus 4.8 were both used.

The caveat GitHub volunteered is the one to keep. By September 14 the team had traced dozens of port regressions, all fixed, mostly correctness bugs from reimplemented behavior, partially applied migrations, rebasing losses and tests that confidently validated the wrong thing. Rust's compiler proves a program compiles, not that it is coherent — "if it compiles, it compiles" is useful only as a joke, Toub writes. The port deliberately mirrored the old structure instead of redesigning it, so the ownership and concurrency gains Rust enables are still unclaimed.

What to watch: whether GitHub takes the structural rewrite it deferred, and whether other large runtimes treat a $120,000 agent-assisted port as a template.

Would you sign off on a 800,000-line rewrite where the compiler is the only reviewer? Tell us in the comments.

Read more

OpenAI in early talks to buy security firm Trail of Bits

OpenAI in early talks to buy security firm Trail of Bits

OpenAI's security ambitions got a name attached to them today, Google opened its frontier models to European scientists, and a Chinese lab put an agent inside a phone and sold it by the token plan. OpenAI is in early talks to acquire Trail of Bits, the New York security firm that has spent fourteen years finding and fixing vulnerabilities in open-source software. The Information reported the discussions Tuesday, citing people familiar with the matter; the deal size is undisclosed, the talks ar

Deep Dive — Drones just proved AI compute is a wartime target

Deep Dive — Drones just proved AI compute is a wartime target

Four days of Ukrainian drone strikes took out half of Yandex's data centers, including the buildings that hold all three of its training supercomputers. The rest of the industry is now asking a question it had been avoiding: what happens when the machines that make AI are also the easiest thing to hit. The four days Russia started it. Through late September, Russian drones and missiles hit Ukrainian data centers and telecom infrastructure, temporarily cutting internet and cell service for u

Tencent slots an AI agent into 14 million companies' contact lists

Tencent slots an AI agent into 14 million companies' contact lists

China's biggest workplace chat app now lists an AI agent as a colleague. Tencent shipped a deep two-way integration between WeCom and its WorkBuddy office agent, and it went out to the version of WeChat that businesses actually run on. WorkBuddy now sits in the WeCom contact list as a conversational bot — not a sidebar plugin. In WeCom 5.0.12, the agent appears next to human colleagues and can be messaged like one; WorkBuddy 5.8.0 in turn logs in with a WeCom account and inherits permissions a

Drone strikes knock out three Yandex data centers in four days

Drone strikes knock out three Yandex data centers in four days

Russia moved its digital economy onto a handful of centralized campuses. Ukraine just demonstrated what that concentration costs — and two of the buildings hit hold the machines Yandex trains its AI on. Ukrainian drone strikes have knocked out three of Yandex's data centers in four days, including the sites that house the supercomputers the company uses to train YandexGPT. The first attack damaged the Sasovo facility southeast of Moscow on October 8. That campus holds two of Yandex's three AI