On 28 October 2026 GitHub announced that the GitHub Copilot SDK is becoming the Microsoft Copilot SDK. It is described as the programmable interface for the Microsoft Copilot harness, the shared agent foundation across Microsoft and GitHub products. The stated aim is to let developers build agent experiences on the same foundation as GitHub’s own, while keeping control of prompts, tools, policies and the application experience.
What changes, and when
GitHub gives no dates. The SDK repository is being updated ahead of an “upcoming move to the Microsoft organization”, and branding and documentation updates have started. The migration will happen in phases.
What does not change
No immediate action is required for existing users. Package names, namespaces and some documentation may still say GitHub Copilot SDK during the transition, and support is unchanged.
What it means
Microsoft is consolidating its AI agent tooling under one name and one foundation. For anyone building an AI feature into a product, the practical risk is not the rename itself. It is the knock-on effect: documentation that disagrees with packages, and a dependency whose ownership is shifting underneath you.
So what
If your product, or a product you are commissioning, builds on this SDK, ask your supplier to record it as a named dependency and to watch for the package and namespace changes GitHub has flagged. Treat vendor SDKs as things that move, and keep the integration layer thin. Our AI app development service builds AI features that way. To discuss yours, start a project.