Claude Code using API credits instead of Claude Max subscription

Resolved 💬 3 comments Opened Nov 24, 2025 by drforbo Closed Nov 28, 2025

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

I have a Claude Max subscription but Claude Code is consuming my API credits instead of using my Max plan.

What Should Happen?

Account Setup:

  • I have an active Claude Max subscription (verified at claude.ai/settings/plan)
  • The same account also has API credits
  • Using the same credentials for both claude.ai and console.anthropic.com

Expected Behavior:

  • Claude Max subscribers should have unlimited Claude Code usage
  • API credits should NOT be consumed when logged in with a Max account
  • Claude Code should use the Max subscription, not API credits

Actual Behavior:

  • API credits are decreasing with each Claude Code conversation
  • Despite being logged in with Claude Max credentials, the system appears to be treating me as an API user

Environment:

  • OS: macOS (Darwin 24.6.0)
  • Claude Code version: [latest]
  • Account type: Claude Max + API credits (same account)

Additional Context:

  • Login appears successful with no errors
  • Both claude.ai and console.anthropic.com show the same account is logged in
  • This appears to be a bug where Claude Code is not properly recognizing the Max subscription

Error Messages/Logs

Steps to Reproduce

Steps to Reproduce:

  1. Log in to Claude Code using /login
  2. See "Login successful" message
  3. Use Claude Code for conversations
  4. Check API credit usage at console.anthropic.com

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Latest

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗