// the take
The official SDK (Node, Python, Go, .NET, Rust, Java) for embedding GitHub Copilot's agent runtime into your own application: it talks JSON-RPC to the Copilot CLI running in server mode, so Copilot handles planning, tool calls and file edits instead of you building an agent loop. It's for teams building products on top of Copilot's existing agent, not people looking for a general-purpose LLM agent framework.
Six official SDKs share one JSON-RPC protocol against the same CLI server, and three of them (Node, Python, .NET) bundle the CLI as a dependency so there's no separate binary to install or pin. BYOK support means you can point it at OpenAI, Azure Foundry or Anthropic keys without a GitHub Copilot subscription, so it isn't a pure walled garden. The test suite is unusually deep for an SDK - dozens of E2E files covering hooks, MCP, cloud sessions, permissions and structured output - which suggests the protocol surface is actually exercised rather than just documented. Custom agents, skills and MCP tools are first-class, so you aren't limited to Copilot's built-in toolset.
It's a thin client over a CLI subprocess, not a standalone agent library - even with BYOK configured you're still routing through GitHub/Microsoft's CLI process and its lifecycle management, not calling a model directly. The project is mid-rename to 'Microsoft Copilot SDK' with an announced org move to Microsoft already underway; package names and namespaces are explicitly called out as stable 'during the transition' only, which is the kind of wording that precedes a breaking change later. Elicitation schema handling is inconsistent across languages - Node and Rust preserve wire schema metadata and property order, while Python, Go, .NET and Java reconstruct the schema and drop that guarantee - a real trap if you're building a cross-language integration expecting identical behavior. Auth is GitHub OAuth or key-based BYOK only; there's no Entra ID or managed identity support, which is a gap for enterprises standardized on Azure AD.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →