The GitHub Copilot SDK provides production-ready, multi-platform client libraries (Node.js/TypeScript, Python, Go, .NET, Java, Rust) that let applications embed Copilot’s agent runtime programmatically. SDKs communicate with the Copilot CLI server via JSON-RPC; the SDK manages the CLI process lifecycle or can connect to an external CLI server. The repo includes language-specific folders and cookbooks, installation commands (e.g. , , , , , Maven coordinates for Java), and a Getting Started guide and docs.
Translation
Translation
Translated body generated separately from the summary.
No translation available yet.
README
github/copilot-sdk
Captured original README content.
GitHub Copilot CLI SDKs
Agents for every app.
Embed Copilot's agentic workflows in your application with the GitHub Copilot SDK for Python, TypeScript, Go, .NET, Java, and Rust.
The GitHub Copilot SDK exposes the same engine behind Copilot CLI: a production-tested agent runtime you can invoke programmatically. No need to build your own orchestration—you define agent behavior, Copilot handles planning, tool invocation, file edits, and more.
Embed agentic workflows without building orchestration: define agent behavior and let Copilot handle planning, tool invocation, and file edits. The SDK exposes the same engine behind Copilot CLI.
Flexible deployment and auth: supports GitHub-signed users, OAuth GitHub Apps, environment tokens (COPILOT_GITHUB_TOKEN, GH_TOKEN, GITHUB_TOKEN), and BYOK (Bring Your Own Key) to use third-party LLM provider keys (OpenAI, Azure AI Foundry, Anthropic).
Practical for app developers, backend engineers, and teams building IDE integrations or automation: Node/Python/.NET SDKs bundle the Copilot CLI automatically, while Go/Java/Rust require installing the CLI or using bundling features.
Notable Details from the README
The SDK is generally available and follows semantic versioning (see CHANGELOG.md).
By default the SDK exposes the CLI's first-party tools (permission handler lets apps approve/deny tool calls).
There are cookbooks, an extensive docs index, and language-specific guidance (awesome-copilot cookbooks and instruction links).
Why It's Trending Now
The project is seeing continued adoption (Rank #10 today, ~8.9k stars total and 38 stars added today) as teams look to embed agentic Copilot workflows across languages with production-ready SDKs, BYOK support, and clear guides for installation and authentication.
For Node.js, Python, and .NET SDKs, the Copilot CLI is bundled automatically and no separate installation is required.
For Go, Java, and Rust, install the CLI manually or ensure copilot is available in your PATH. Go and Rust also expose application-level CLI bundling features.
Install your preferred SDK using the commands above.
See the SDK README for usage examples and API documentation.
Architecture
All SDKs communicate with the Copilot CLI server via JSON-RPC:
Your Application
↓
SDK Client
↓ JSON-RPC
Copilot CLI(server mode)
The SDK manages the CLI process lifecycle automatically. You can also connect to an external CLI server—see the Getting Started Guide for details on running the CLI in server mode.
FAQ
Do I need a GitHub Copilot subscription to use the SDK?
Yes, a GitHub Copilot subscription is required to use the GitHub Copilot SDK, unless you are using BYOK (Bring Your Own Key). With BYOK, you can use the SDK without GitHub authentication by configuring your own API keys from supported LLM providers. For standard usage (non-BYOK), refer to the GitHub Copilot pricing page, which includes a free tier with limited usage.
How does billing work for SDK usage?
Billing for the GitHub Copilot SDK is based on the same model as the Copilot CLI, with each prompt being counted towards your premium request quota. For more information on premium requests, see Requests in GitHub Copilot.
Does it support BYOK (Bring Your Own Key)?
Yes, the GitHub Copilot SDK supports BYOK (Bring Your Own Key). You can configure the SDK to use your own API keys from supported LLM providers (e.g. OpenAI, Azure AI Foundry, Anthropic) to access models through those providers. See the BYOK documentation for setup instructions and examples.
Note: BYOK uses key-based authentication only. Microsoft Entra ID (Azure AD), managed identities, and third-party identity providers are not supported.
What authentication methods are supported?
The SDK supports multiple authentication methods:
GitHub signed-in user - Uses stored OAuth credentials from copilot CLI login
OAuth GitHub App - Pass user tokens from your GitHub OAuth app
No — for Node.js, Python, and .NET SDKs, the Copilot CLI is bundled automatically as a dependency. You do not need to install it separately.
For Go, Java, and Rust SDKs, the CLI is not bundled by default. Install the CLI manually or ensure copilot is available in your PATH. Go and Rust also expose application-level CLI bundling features.
Advanced: You can override the CLI binary or connect to an external server. See the individual SDK README for language-specific options.
What tools are enabled by default?
By default, the SDK exposes the Copilot CLI's first-party tools, similar to running the CLI with --allow-all. Tool execution is still governed by each SDK's permission handler, so applications can approve, deny, or customize tool calls. You can customize tool availability by configuring the SDK client options to enable and disable specific tools. Refer to the individual SDK documentation for details on tool configuration and to the Copilot CLI documentation for the list of available tools.
Can I use custom agents, skills or tools?
Yes, the GitHub Copilot SDK allows you to define custom agents, skills, and tools. You can extend the functionality of the agents by implementing your own logic and integrating additional tools as needed. Refer to the SDK documentation of your preferred language for more details.
Are there instructions or SDK guidance for Copilot to speed up development?
Yes, check out the custom instructions and SDK-specific guidance:
All models available via Copilot CLI are supported in the SDK. The SDK also exposes a method which will return the models available so they can be accessed at runtime.
Is the SDK production-ready?
The GitHub Copilot SDK is generally available and follows semantic versioning. See CHANGELOG.md for release notes.
How do I report issues or request features?
Please use the GitHub Issues page to report bugs or request new features. We welcome your feedback to help improve the SDK.
