What this error means
Silent ANTHROPIC_API_KEY env var takes precedence over Max subscription auth — users with both set get unexpected API-key billing instead of their included Max quota is a Claude Code failure pattern reported for developers trying to understand claude code auth priority when both api key and subscription exist; prevent unexpected billing by ensuring max subscription takes priority over api key. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.
Why this happens
GitHub Issue #53728 in anthropics/claude-code (opened Apr 27 2026, yellowhardhat). Environment variable precedence issue silently switches users to pay-per-API-key billing even though they have Max subscription with included quota. Critical cost impact — users unknowingly incur API charges. Tagged enhancement for area:auth + area:cost. Category mapping: AI Coding Tools (silent billing switch on paid subscription product).
Common causes
- GitHub Issue #53728 in anthropics/claude-code (opened Apr 27 2026, yellowhardhat). Environment variable precedence issue silently switches users to pay-per-API-key billing even though they have Max subscription with included quota. Critical cost impact — users unknowingly incur API charges. Tagged enhancement for area:auth + area:cost. Category mapping: AI Coding Tools (silent billing switch on paid subscription product).
Quick fixes
- Confirm the exact error signature matches
Silent ANTHROPIC_API_KEY env var takes precedence over Max subscription auth — users with both set get unexpected API-key billing instead of their included Max quota. - Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
- Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests.
Platform/tool-specific checks
- Verify the command, editor, extension, or API client that produced the error.
- Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
- Avoid deleting credentials, local model data, or project settings until the failing scope is clear.
Step-by-step troubleshooting
- Capture the exact error message and the command, editor action, or request that triggered it.
- Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
- Review the source evidence below and compare it with your environment.
- Apply one change at a time and rerun the smallest failing action.
- Keep the working fix documented for the team or deployment environment.
How to prevent it
- Keep provider/tool configuration documented.
- Record non-secret diagnostics such as tool version, provider name, model name, and command path.
- Add a lightweight check before CI or production workflows depend on the tool.