Summary
Claude Code incorrectly enforces rate limits from one Max account onto a different Max account when both are used on the same device.
Environment
- Claude Code version: 2.0.55
- OS: macOS
- Two separate Claude Max subscriptions on different accounts
Steps to Reproduce
- Have two Claude Max accounts (Account A and Account B)
- Use Claude Code with Account A until hitting weekly limit
claude logout
claude login with Account B (which has 4% usage, well under limit)
- Attempt to send a message
Expected Behavior
Account B should work normally since it has 96% of its quota remaining.
Actual Behavior
Claude Code shows "weekly limit reached" despite Account B having only 4% usage according to claude.ai/settings.
Troubleshooting Attempted
claude logout / claude login with Account B - still blocked
- Deleted
~/.claude/statsig/ directory and re-logged in - still blocked
- Revoked ALL authorization tokens at claude.ai/settings/claude-code and fresh login - still blocked
- Verified Account B shows 4% usage at claude.ai/settings (Usage page)
Evidence
The account's usage page confirms only 4% weekly usage and 0% Sonnet usage, yet Claude Code refuses to send messages citing the weekly limit.
Hypothesis
There appears to be device-level or machine-level rate limit tracking that persists across account switches, incorrectly applying Account A's exhausted quota to Account B.
Summary
Claude Code incorrectly enforces rate limits from one Max account onto a different Max account when both are used on the same device.
Environment
Steps to Reproduce
claude logoutclaude loginwith Account B (which has 4% usage, well under limit)Expected Behavior
Account B should work normally since it has 96% of its quota remaining.
Actual Behavior
Claude Code shows "weekly limit reached" despite Account B having only 4% usage according to claude.ai/settings.
Troubleshooting Attempted
claude logout/claude loginwith Account B - still blocked~/.claude/statsig/directory and re-logged in - still blockedEvidence
The account's usage page confirms only 4% weekly usage and 0% Sonnet usage, yet Claude Code refuses to send messages citing the weekly limit.
Hypothesis
There appears to be device-level or machine-level rate limit tracking that persists across account switches, incorrectly applying Account A's exhausted quota to Account B.