Description
docs/src/content/docs/setup/quick-start.mdx:213 and docs/src/content/docs/setup/cli.md:282 both state CLAUDE_CODE_OAUTH_TOKEN "is not supported and is ignored if set" — verified live on main (commit f2e8122) — but neither describes what actually happens when a Claude Code CLI user (who naturally has this token from claude login) runs a workflow anyway: does it fail with an unrelated auth error, or silently no-op? This is exactly the credential such a user reaches for first, so the missing failure-mode description turns a known limitation into a confusing debugging session. (Distinct from closed #46613, which added the "unsupported" note itself — this asks for the consequence to be documented, not the existence of the limitation.)
Fix
Add one sentence at both doc locations describing the actual observed behavior when CLAUDE_CODE_OAUTH_TOKEN is set without ANTHROPIC_API_KEY/WIF (e.g. the specific error message or exit behavior the engine produces), so users can recognize the symptom and know to switch credentials immediately rather than debugging blind.
Expected Impact
Removes a silent trap for the most natural first auth attempt by existing Claude Code CLI users, reducing support/debugging friction documented in today's Claude Code User Documentation Review.
Suggested Agent
Claude Code Docs Review workflow follow-up / Copilot coding agent.
Estimated Effort
Quick (< 1 hour)
Data Source
DeepReport Intelligence Briefing 2026-08-21, mining discussion #54536 (Claude Code User Documentation Review), Critical Blocker #1.
Generated by 🔬 Deep Report · agent · 106.7 AIC · ⌖ 8.62 AIC · ⊞ 12.4K · ◷
Description
docs/src/content/docs/setup/quick-start.mdx:213anddocs/src/content/docs/setup/cli.md:282both stateCLAUDE_CODE_OAUTH_TOKEN"is not supported and is ignored if set" — verified live onmain(commit f2e8122) — but neither describes what actually happens when a Claude Code CLI user (who naturally has this token fromclaude login) runs a workflow anyway: does it fail with an unrelated auth error, or silently no-op? This is exactly the credential such a user reaches for first, so the missing failure-mode description turns a known limitation into a confusing debugging session. (Distinct from closed #46613, which added the "unsupported" note itself — this asks for the consequence to be documented, not the existence of the limitation.)Fix
Add one sentence at both doc locations describing the actual observed behavior when
CLAUDE_CODE_OAUTH_TOKENis set withoutANTHROPIC_API_KEY/WIF (e.g. the specific error message or exit behavior the engine produces), so users can recognize the symptom and know to switch credentials immediately rather than debugging blind.Expected Impact
Removes a silent trap for the most natural first auth attempt by existing Claude Code CLI users, reducing support/debugging friction documented in today's Claude Code User Documentation Review.
Suggested Agent
Claude Code Docs Review workflow follow-up / Copilot coding agent.
Estimated Effort
Quick (< 1 hour)
Data Source
DeepReport Intelligence Briefing 2026-08-21, mining discussion #54536 (Claude Code User Documentation Review), Critical Blocker #1.