Choose the authentication method that best fits your deployment scenario for the GitHub Copilot SDK.
- Authenticate Copilot SDK: methods, priority order, and examples
- Server-to-server authentication: use GitHub Actions or GitHub App installation tokens for organization-attributed automation
- Bring your own key (BYOK): use your own API keys from OpenAI, Azure, Anthropic, and more
When multiple credentials are configured, an explicit SDK token takes priority, followed by direct Copilot API environment authentication, environment variable GitHub tokens, stored Copilot CLI credentials, and then GitHub CLI credentials. GitHub App installation tokens outside GitHub Actions use the explicit SDK token, or COPILOT_GITHUB_TOKEN on the runtime process for an existing runtime URI. See Authenticate Copilot SDK for details.
For multi-user server mode, pass a per-session gitHubToken so each session runs with the correct GitHub identity; see Multi-user and server deployments.