You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[plan] Expand auth.mdx to cover provider-based and OAuth authentication for all engines #25058
Expand docs/src/content/docs/reference/auth.mdx to cover provider-based and OAuth authentication for all supported engines (Copilot, Claude, Codex), which is currently undocumented.
Context
Issue #16498 has been open since February 2026. The gap is now more urgent because Copilot CLI 1.0.19 (issue #25014) added BYOK, which overlaps with provider-based auth. auth.mdx currently only covers the API key method; OAuth and cloud-provider auth paths are missing entirely.
CLAUDE_CODE_OAUTH_TOKEN is used in workflow code but not documented. Users have no guidance on which secrets to configure for each engine.
Restructure auth.mdx with engine-specific sections:
Copilot: GitHub token auth (current), plus BYOK via COPILOT_PROVIDER_* env vars (link to BYOK page created in the companion issue)
Claude: ANTHROPIC_API_KEY (API key), CLAUDE_CODE_OAUTH_TOKEN (OAuth — document this explicitly), and any provider-based options
Codex: OPENAI_API_KEY and any Azure/provider variants
Add a "Which secret do I need?" quick-reference table: engine → required secret(s) → optional alternatives — this is the most common question new users have.
Document CLAUDE_CODE_OAUTH_TOKEN: when to use OAuth vs API key, how to obtain the token, and how to store it as a repository secret.
Document Codex authentication options including Azure variants if supported.
Add a "Troubleshooting auth errors" section with common error messages and fixes.
Acceptance Criteria
All three engines (Copilot, Claude, Codex) have their own auth section
CLAUDE_CODE_OAUTH_TOKEN is documented with instructions for obtaining and using it
Activity
github-actions commentedon Apr 7, 2026
🍪 Issue Monster has assigned this to Copilot!
I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.
The Copilot coding agent will analyze the issue and create a pull request with the fix.
Om nom nom! 🍪