Claude Code auth silently reverts to Console API — $100s billed against wrong account

What this error means

Login selects claude.ai subscription but /status shows Anthropic Console API for billing; user incurs hundreds of dollars in unauthorized API spend is a Claude Code failure pattern reported for developers trying to fix claude code defaulting to console api billing instead of claude.ai max subscription after login. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub Issue #60422 on anthropics/claude-code opened May 19, 2026. User reports explicit /login → select claude.ai → authorize flow followed by /status showing wrong billing path. Multiple commenters confirmed same pattern with ~$1,050 over 3 days loss. Mapping: Claude Code billing/authentication error → AI Coding Tools (approved category).

Common causes

• GitHub Issue #60422 on anthropics/claude-code opened May 19, 2026. User reports explicit /login → select claude.ai → authorize flow followed by /status showing wrong billing path. Multiple commenters confirmed same pattern with ~$1,050 over 3 days loss. Mapping: Claude Code billing/authentication error → AI Coding Tools (approved category).

Quick fixes

1. Confirm the exact error signature matches Login selects claude.ai subscription but /status shows Anthropic Console API for billing; user incurs hundreds of dollars in unauthorized API spend.
2. Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
3. Verify the account session, API key, provider settings, and environment where the failing tool is running.

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/60422

Evidence note: GitHub Issue #60422 on anthropics/claude-code opened May 19, 2026. User reports explicit /login → select claude.ai → authorize flow followed by /status showing wrong billing path. Multiple commenters confirmed same pattern with ~$1,050 over 3 days loss. Mapping: Claude Code billing/authentication error → AI Coding Tools (approved category).

Related errors

• AI Coding Tools

FAQ

What should I check first?

Start with the exact Login selects claude.ai subscription but /status shows Anthropic Console API for billing; user incurs hundreds of dollars in unauthorized API spend 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 Login selects claude.ai subscription but /status shows Anthropic Console API for billing; user incurs hundreds of dollars in unauthorized API spend.