Microsoft Ships Copilot SDK 2.0 With In-Process Runtime
In-process runtime becomes the default
Microsoft published its Copilot SDK 2.0 release on Command Line on November 17, 2026, under the title "Introducing the Microsoft Copilot SDK 2.0" (Command Line). The official SDK release record lists version 2.0.0 as a major version change: the Copilot runtime now executes inside the host application's own process by default, rather than being spawned as a separate child process as in prior versions (GitHub).
That shift is the headline engineering change in this release. Previous SDK versions isolated the runtime by default through process separation; Copilot SDK 2.0 inverts that default, favoring in-process execution unless developers opt out.
Multi-session isolation within one process
Microsoft says the new runtime architecture can host multiple sessions inside a single process at once. Each session maintains its own state, credentials, tools, files, and history, and the sessions cannot reach into one another's data (Command Line). This is designed to let a single application process serve many concurrent agent sessions without one session's tool access or file history leaking into another's.
Sandboxing for shell and file operations
The SDK keeps the model loop running on the shared, in-process runtime, but shell and file commands are routed to execute inside a sandbox. Microsoft specifically names sandboxed host implementations of `bash`, `view`, and `edit` as the commands that run this way (Command Line). Available documentation also describes an SDK capability for moving a session out of shared hosting and into an isolated sandbox when shell or file access is required, though the exact wording Microsoft used for that mechanism is not established in the release materials (GitHub).
Migration note and platform fix
Because process isolation is no longer the default, the official release record flags changes developers may need to make when upgrading. Teams that depend on out-of-process execution can restore it by calling `RuntimeConnection.forSpawnedStdio()` (GitHub). The same release notes report a Windows-specific fix addressing `PATH` handling inconsistencies in sandboxed child environments, standardizing how the sandbox resolves executable paths on that platform (GitHub).
Coverage of the release has also appeared from Ignite 2026 reporting noting general availability of the SDK (Thurrott), alongside independent technical write-ups on the shared-runtime model (AgentRiot). The package is published on PyPI (PyPI) and NuGet (NuGet) for developers to install directly.


