[Bug] Auth token not cleared on account switch; old account usage consumed
Status Open
Reported on v2.1.300
Maintainer reply None cached
Activity 0 comments · opened Oct 15, 2026
Follow-up to Feedback ID 3701e7f5-811c-437b-ba55-da87572fecf5
Corrections: neither account is on a Team plan, the account emails were mislabelled, and the timezone is now included.
Title: After switching accounts in Claude Code, the new account's session limit is used up almost immediately (old account's auth appears to be cached)
Environment
- Product: Claude Code 2.1.300 (CLI), terminal xterm-256color
- OS: macOS 26.0 (build 25A8353), Apple Silicon (arm64)
- Account A (previous): xxxx · Max (20x)
- Account B (new): xxxx· Max (5x)
Steps to reproduce
- Use Claude Code logged in as account A (Max 20x).
- Run
/logout, then/loginas account B (Max 5x). - Send a few prompts.
- Check the usage page on claude.ai for account B.
Expected
- Account B's usage grows in proportion to the prompts actually sent after the switch.
Actual (observed)
- Account B's usage page (screenshot attached, plan shown as "Max (5x)"):
- Current session: 100% used, resets Fri 1:50 AM ICT, so the 5-hour window started around 20:50 ICT, right at the switch
- This week: 71% used, resets Wednesday 10:00 AM ICT
- Banner: "At this pace you'll run out tomorrow afternoon, before Wednesday's reset."
- The session limit was reached almost immediately after switching, far faster than the prompts sent could explain.
Suspected cause (not confirmed)
- Auth or session state from account A seems to persist after
/logout→/login, so the load from A's ongoing work may be counted against account B.
Timeline (Vietnam time, ICT = UTC+7)
- ~21:00 ICT, Thu 2026-10-15 (14:00 UTC): switched from account A to account B
- Shortly after, in the same session: account B's current-session usage reached 100%
Request
- Please check which account the requests made after the switch were actually billed to.
- Please restore account B's consumed session/weekly usage if this was caused by the bug.
---