[BUG] Pro subscriber: org_level_disabled prevents Claude Code from using subscription (never worked since signup)
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?
Claude Code has never worked with my Pro subscription since signup. It always shows "API Usage Billing instead of my Pro plan and gives "credit balance too low" immediately.
cat ~/.claude.json shows:
"hasExtraUsageEnabled": false
"cachedExtraUsageDisabledReason": "org_level_disabled"
What I've tried:
- claude logout / claude login multiple times
- rm ~/.claude.json and re-authenticating
- Extra Usage option not available in claude.ai Settings
- Contacted support — case closed as resolved without fixing anything
Platform: macOS, Claude Code v2.1.76
Related issues: #5300, #7719
What Should Happen?
Claude Code should recognize my active Claude.ai Pro subscription and use its included usage allocation instead of requiring API credits.
The welcome screen should show "Pro Plan" not "API Usage Billing", and I should be able to use Claude Code without hitting a credit balance error.
Error Messages/Logs
Credit balance too low · Add funds: https://platform.claude.com/settings/billing
Steps to Reproduce
- Have an active Claude.ai Pro subscription ($20/month)
- Install Claude Code (npm install -g @anthropic-ai/claude-code)
- Run: claude login
- Authenticate using Claude.ai account credentials in the browser
- Run: claude
- Welcome screen shows "API Usage Billing" instead of Pro plan
- Any attempt to use Claude Code immediately shows "credit balance too low" error
Claude Model
Sonnet (default)
Is this a regression?
No, this never worked
Last Working Version
_No response_
Claude Code Version
2.1.76.
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
Contents of ~/.claude.json (relevant lines):
"hasExtraUsageEnabled": false,
"cachedExtraUsageDisabledReason": "org_level_disabled",
"oauthAccount": {
"accountUuid": "98e17476-0ec2-4e10-9532-bc19f60f7bb2",
"emailAddress": "akhildasari864@gmail.com",
"organizationUuid": "b1baf97c-2312-4358-b828-76f986d6d4ec",
"hasExtraUsageEnabled": false
}
Related GitHub issues: #5300, #7719
Note: Anthropic support previously closed a ticket for this issue
as "resolved" but the problem persists and the config flags are unchanged.
7 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
This is not a duplicate. Unlike the referenced issues, my account has "cachedExtraUsageDisabledReason":"org_level_disabled" which prevents Extra Usage from being enabled entirely - not just a login/auth problem. Support closed a previous ticket as resolved without fixing anything. Please do not auto-close.
None of these are duplicates - they are unrelated issues. My issue is specifically about Claude Code defaulting to API Usage
Billing instead of Pro subscription from first login, with "cachedExtraUsageDisabledReason": "org_level_disabled" set on my
account. Please do not auto-close.
Related: the org_level_disabled flag appears to be a broader backend bug affecting multiple Pro subscribers across different features.
See #28098, #29037, #29185, #29449, #30820 where the same flag breaks Remote Control for Pro users. The root cause is identical — isPolicyAllowed() returning false for personal Pro accounts that should have no org-level restrictions.
This needs a backend fix that resets org policy flags for affected Pro subscriber accounts.
It has been 10 days with no response from Anthropic. Support ticket was closed as resolved without any fix. Requesting immediate escalation. This same bug is confirmed in #28098, #29037, #29185, #29449, #30820. Please assign an engineer to this.
I found a soultion myself. I hope you can provide me a solution at a faster pace, if there is a next time. Thank you.
Best.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.