[BUG] Session limit accounting breaks after adding a Team plan to a Max (20x) account: /usage reports 100% consumed while claude.ai reports 0% for the same window

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?

On a single account that holds both a Max (20x) subscription and a Team plan,
the three Claude surfaces report contradictory values for the current session limit.

| Surface | Plan shown | Current session | Weekly (all models) | Weekly reset |
|------------------------------------|------------|-----------------|---------------------|----------------|
| claude.ai (web) → Settings → Usage | Max (20x) | 0% used | 68% used | Sat 9:59am |
| Desktop app → Settings → Usage | Team | 100% used | 13% used | Tue 3:00pm |
| Claude Code CLI /usage | — | 100% used | 13% used | Sep 1 at 3pm |

The session figures refer to the same window. The web screenshot showed
"resets in 4h 52m" when taken at ~21:12 KST; the desktop screenshot showed
"resets in 4h 23m" at ~21:41 KST. Both resolve to a reset at ~02:04 KST, and
Claude Code independently reports "Resets 2am (Asia/Seoul)".

So all three surfaces agree on WHEN the current session resets, but two report
it as fully consumed while the third reports it as untouched. If these were
separate per-plan session pools, I would not expect their reset instants to
coincide to the minute.

The weekly limits do appear to be genuinely separate pools — those reset times
differ (Sat 9:59am vs Tue 3:00pm) and the percentages differ accordingly.

A second symptom points to the same root cause. Immediately after the Team plan
was added to this account, Claude Code reported the session limit as 100%
consumed on the first command run. A background /loop task had been running
beforehand (~2.6M cumulative tokens per /usage), so consumption was not zero —
but the session reached its cap while the corresponding weekly figure sat at
only 13%, and while the Max (20x) session window on the same account read 0%.

Both symptoms are consistent with the session counter being attributed to the
wrong plan, or with prior consumption being carried into a newly added plan's
session window rather than starting fresh.

Impact: Claude Code is blocked on a session limit it reads as 100% consumed,
while the corresponding weekly usage is only 13% and the Max (20x) session
window reads 0%. There is no setting in Claude Code or the desktop app to
choose which plan a surface draws from, so there is no workaround.

<img width="1154" height="900" alt="Image" src="https://github.com/user-attachments/assets/14f036b2-e9cb-419c-a7ef-daa9986f0585" />

<img width="392" height="367" alt="Image" src="https://github.com/user-attachments/assets/6d4de9cb-23cb-4f2d-9cc9-98e06a0ebbd8" />

<img width="1148" height="862" alt="Image" src="https://github.com/user-attachments/assets/5b7b2a13-e0a2-4a3d-9fca-49c7e6c845fe" />

What Should Happen?

All surfaces signed in to the same account should report the same value for the
same session window. If a session limit genuinely belongs to a specific plan,
the UI should state which plan it applies to and let the user choose which plan
Claude Code draws from — especially when the account holds two plans and one of
them still has session capacity available.

Additionally, adding a plan to an existing account should not leave the new
plan's session window pre-consumed. Either the session counter should start
fresh for the newly added plan, or the UI should state explicitly that prior
consumption carries over — currently it does neither, and the account is left
blocked despite holding a second plan with an unused session window.

Error Messages/Logs

1. Use an account that holds BOTH a Max (20x) subscription and a Team plan.
2. Sign in to that same account on all three surfaces: claude.ai in a browser,
   the Claude desktop app, and Claude Code in a terminal.
3. In Claude Code, run `/usage`. Note the "Current session" percentage and the
   reset time.
4. In the desktop app, open Settings → Usage. Note the same two values.
5. On claude.ai, open Settings → Usage. Note the same two values.
6. Convert the countdowns ("resets in Xh Ym") into absolute times and compare
   them against Claude Code's stated reset time.

Result: all three resolve to the same session reset instant (~02:04 KST in my
case), but claude.ai reports 0% consumed while the desktop app and Claude Code
report 100% consumed. Claude Code then refuses further requests.

Note: no specific repository, file, or code is involved — this reproduces on any
project, since it concerns account-level usage reporting rather than a workspace.

Steps to Reproduce

1. Start from an account with an active Max (20x) subscription.
2. Add a Team plan to that same account via the desktop app.
3. Immediately run any command in Claude Code and run /usage.

Observed: session limit already reads 100% consumed, and further requests
are declined — while weekly usage for the same plan reads 13%.
---

1. Use an account that holds BOTH a Max (20x) subscription and a Team plan.
2. Sign in to that same account on all three surfaces: claude.ai in a browser,

the Claude desktop app, and Claude Code in a terminal.

1. In Claude Code, run /usage. Note the "Current session" percentage and the

reset time.

1. In the desktop app, open Settings → Usage. Note the same two values.
2. On claude.ai, open Settings → Usage. Note the same two values.
3. Convert the countdowns ("resets in Xh Ym") into absolute times and compare

them against Claude Code's stated reset time.

Result: all three resolve to the same session reset instant (~02:04 KST in my
case), but claude.ai reports 0% consumed while the desktop app and Claude Code
report 100% consumed. Claude Code then refuses further requests.

Note: no specific repository, file, or code is involved — this reproduces on any
project, since it concerns account-level usage reporting rather than a workspace.

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.245 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

Screenshots attached:

1. claude.ai (web) → Settings → Usage — Max (20x): session 0% used,

weekly 68% used, "resets in 4h 52m", weekly reset Sat 9:59am

1. Claude Code CLI /usage — session 100% used, weekly 13% used,

"Resets 2am (Asia/Seoul)", weekly reset Sep 1 at 3pm

1. Claude desktop app → Settings → Usage — Team: session 100% used,

weekly 13% used, "resets in 4h 23m", weekly reset Tue 3:00pm

All three were captured within roughly 30 minutes of each other while signed in
to the same account, and all three point to the same session reset instant.

Context: this started after adding a Team plan to an account that already had a
Max (20x) subscription. I've filed the plan-conversion side of this separately
with support; this issue is specifically about Claude Code reporting a session
limit value that contradicts claude.ai for the same window.

Timezone: Asia/Seoul (UTC+9). Observed 2026-08-25, ~21:10–21:41 KST.

Context: both symptoms appeared after adding a Team plan to an account that
already had a Max (20x) subscription. I have raised the billing/entitlement side
separately with support; this issue covers the session-limit accounting and
reporting behavior itself.