Microsoft Copilot SDK 2.0 makes agent sessions durable, not disposable
The renamed GitHub Copilot SDK moves to a shared, Rust-built runtime where sessions outlive any process, and startup time drops from 5.25 seconds to 55 milliseconds.
Microsoft shipped version 2.0 of what was the GitHub Copilot SDK, rebranded as the Microsoft Copilot SDK, on 17 November. The core change is architectural: instead of one container per agent session, a shared runtime now serves many sessions at once, each with isolated state, credentials and tools.
Microsoft rebuilt that runtime in Rust, and the numbers are specific: creating a client and a session and completing one turn dropped from 5.25 seconds on the old TypeScript CLI to 55.3 milliseconds. Sessions are also now durable, persisting through a session journal independent of any one process, so a web app can disconnect while a long-running task keeps going and resume it later by session ID. Credentials are passed per session rather than held by the server, so actions attribute to the actual end user. The SDK covers TypeScript, Python, Go, .NET, Java and Rust, with a native C ABI for embedding it in other languages.
client.sessions.create({ credentials, tools: allowList })
Why it matters: if you’re building a multi-tenant agent product, this removes two problems you’d otherwise have to solve yourself: cheap session startup at scale, and sessions that survive a server restart or a dropped connection. The per-session credential model also means you don’t need to proxy end-user identity through your own backend just to keep an audit trail.
The caveat: this is a rename and a major version bump in the same release. If you’re on the old GitHub Copilot SDK, check the getting-started guide before upgrading rather than assuming it’s a drop-in update.