The Pulse
Microsoft Copilot SDK 2.0 supports shared agent sessions
Microsoft’s updated Copilot SDK can host multiple agent sessions in a single process rather than requiring a container for each one. The update also adds session-scoped identities and options for resuming conversations across processes.

Microsoft Copilot SDK 2.0 lets developers run multiple agent sessions in a single process instead of requiring a separate container for each session. Microsoft introduced the update at Ignite on November 17, renaming the former GitHub Copilot SDK and adding session-specific identities, tools and storage options.
Previously, every session used its own container, even when its work did not require one. The new runtime can support applications ranging from chat assistants to more complex agent systems, while containers remain an option for work that needs a stronger boundary around code execution or files.
Shared sessions and performance
The runtime has been rebuilt in Rust. Microsoft says that, on the same warmed workload, creating a client and session and completing one turn took 55.3 milliseconds with the Rust core in-process, compared with 5.25 seconds on the TypeScript command-line interface.
In the same comparison, 10 clients used 126 MB of memory rather than 1,383 MB, while throughput rose from 7.55 to 120 sessions per second. Those figures are Microsoft’s measurements for the stated workload.
The SDK now lets developers pass a user’s credential when creating a session, so its model and tool calls are attributed to that user rather than the server’s identity. A token-provider callback can request fresh credentials as tokens expire.
An empty mode starts sessions without access to a host shell, host file system or default tools. Developers can add tools and specify which ones a session may use; those tools run in the host application’s process.
Keeping sessions across processes
A session journal records messages, tool calls and results, plans and checkpoints. A runtime that can read the journal can resume the session with its history after a restart, from another service instance or on a different machine.
By default, session state is stored on the runtime’s disk. An application can also supply the file system through sessionFs, placing state and session-scoped files in object storage, a database or tenant-scoped paths. The application checks that a caller owns a session before resuming it by its ID.
For a live session shared by multiple clients, the SDK can run behind an Agent Host Protocol host. The separate protocol lets clients attach to a synchronized session; Microsoft says the VS Code agent host uses this approach.
Deployment choices and availability
Developers can keep sessions in a shared process with tools supplied through application APIs, Model Context Protocol servers or web calls. In that arrangement, the application enforces isolation rather than a container boundary, and there is no shell or local file-system access.
In another pattern, an application can start a session on the shared runtime and move it into a sandbox when shell or file work is needed. The session retains its ID, conversation and tools, but the move is one-way and requires a wait while the sandbox starts.
The default runtime runs inside the application process through a C application binary interface. The repository cautions that in-process hosting provides neither crash isolation nor a sandbox; subprocess connections and external servers remain supported.
The SDK supports TypeScript, Python, Go,.NET, Java and Rust. The repository describes the SDK as generally available and says its move to the Microsoft organization is part of a phased transition. Existing users do not need to make immediate changes, though package names and documentation may continue to refer to GitHub Copilot SDK during the transition.
Standard use requires a GitHub Copilot subscription, according to the repository, but developers can instead bring their own API keys from supported model providers. Standard billing counts each prompt toward the user’s usage allowance, and the Copilot pricing page includes a free tier with limited usage.
Sources
Companies in this story
Related stories
- GitHub details protocol for Copilot sessions across devices
- LangChain puts agent records at the center of LangSmith
- Firecrawl kit gives Docker sandbox agents controlled web access
- Microsoft makes Copilot Home generally available as Autopilot rolls out
- Malicious Microsoft Agent Framework releases removed from PyPI