Microsoft launches Copilot SDK 2.0 with multi-tenant Rust runtime at Ignite 2026

Microsoft announced on Tuesday, November 17, 2026, at Ignite 2026, the Copilot SDK 2.0, a new version of the development kit that gives programmatic access to the Copilot harness — the agent layer that powers the company's Copilot products. The SDK was known until now as the GitHub Copilot SDK and now carries the Microsoft name, reflecting that the same runtime underpins Copilot across the company, from GitHub to Microsoft 365.

One runtime, many sessions

The main change is the new multi-tenant runtime: many agent sessions now run inside a single process, each with its own state, credentials, tools, files and history — and no session can see another. Because creating a session no longer requires starting a container, a process or a virtual machine, the cost per session drops and the response to the first turn gets faster.

To make that possible, Microsoft rebuilt the runtime core in Rust. According to the company, on the same warmed workload, creating a client and a session and completing one turn fell from 5.25 seconds on the TypeScript CLI to 55.3 milliseconds with the Rust core in-process; ten clients now use 126 MB of memory instead of 1,383 MB, and throughput rose from 7.55 to 120 sessions per second. These are Microsoft's own numbers, with no independent benchmark published.

Per-session identity and empty mode

Another new feature is per-session identity: each session can run under the identity of the user who requested it, rather than the identity of the process that started the runtime. The developer passes the user's credential when creating the session, and every model call and tool call is attributed to that user. For production, a token provider refreshes short-lived credentials so the server never has to store long-lived ones.

The new “empty” mode starts every session with minimal capabilities: no host shell, no host file system and no default tools. The application adds back exactly what a session should have — its own APIs, MCP servers or web calls — and the registered tools run in the application's process, under its rules.

Durable sessions and six architectures

Sessions are also now durable: a session journal records messages, tool calls, plans and checkpoints in an event log, and sessionFs lets the application decide where that state lives — object storage, a database or tenant-scoped paths. Any instance of the service can resume a session by its ID, even after a restart or on another machine.

On the same runtime, Microsoft describes six agent architectures: shared sessions on one runtime, sessions that start shared and move into a sandbox when they need a shell or files, a shared loop with isolated environments, a coordinator with parallel workers, and a mixed architecture combining both. The SDK can also run behind an Agent Host Protocol (AHP) host, an open protocol that turns a session into a shared, synchronized resource — VS Code's agent host works this way.

Availability

Copilot SDK 2.0 is available in TypeScript, Python, Go, .NET, Java and Rust, with native in-process embedding through a C ABI. Those who prefer not to run their own infrastructure can run agents in two managed environments: the GitHub Copilot cloud sandboxes and the Microsoft Foundry managed agents.

The SDK reached general availability in June 2026, still as the GitHub Copilot SDK, and the harness was opened to developers through Foundry in October. The Rust rewrite of the runtime was the subject of our article: GitHub Copilot rewrote its engine in Rust with AI agents. See also another Ignite announcement: the Copilot plugin catalog.

Sources

Featured image: Microsoft logo, in the public domain (text logo), via Wikimedia Commons.

This article was produced with the assistance of artificial intelligence, cross-checked against public posts on X and sources on the internet, and reviewed against the original sources listed below. Always consult the original sources to confirm the details.

Por Muse