GitHub moves Copilot runtime to Rust and cuts startup time
The rewrite makes Copilot faster to embed in host apps and keeps an out-of-process option for setups that still need it.
GitHub has moved the runtime behind Copilot CLI, the Copilot app, and the Copilot SDK from TypeScript and Node.js to Rust, and says the change cut a measured startup-and-session scenario from 5.25 seconds to 292 milliseconds when embedded in process. The company says the rewrite replaced more than 800,000 lines of production code, took about 14.5 weeks, and was shipped incrementally through 128 pull requests while releases kept going. The new runtime can be embedded directly through a C ABI, while an out-of-process mode still exists, which reduces the need for the earlier Node.js and V8 process boundary and its roughly 100 MB working-set overhead per client. GitHub also says the Copilot SDK now supports TypeScript, Python, Go, .NET, Java, and Rust.
Why it matters
For teams using Copilot CLI, the Copilot app, or the Copilot SDK, the runtime now starts much faster when embedded directly and no longer carries the earlier Node.js and V8 boundary cost. That changes the experience for applications that want lower startup latency and smaller per-client memory use, while still leaving an external process option in place for other deployments. The SDK’s language support now also spans TypeScript, Python, Go, .NET, Java, and Rust.
Keep or strike?
Does this story matter, or is it hype? Mark it before you see what everyone else did.
Sources
- InfoQ