Claude Code ANTHROPIC_API_KEY precedence silently shadows Max subscription auth

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

1. 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.
2. Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
3. 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

1. Capture the exact error message and the command, editor action, or request that triggered it.
2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
3. Review the source evidence below and compare it with your environment.
4. Apply one change at a time and rerun the smallest failing action.
5. 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.

Sources checked

• https://github.com/anthropics/claude-code/issues/53728

Evidence note: 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).

Related errors

• AI Coding Tools

FAQ

What should I check first?

Start with the exact 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 text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed Claude Code workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without 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.