[BUG] Team Premium weekly usage counter stuck at 100% despite no usage after multiple reset cycles

Open 💬 1 comment Opened Jul 8, 2026 by duflow89

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?

My Claude Team Premium account appears to have its weekly usage counter stuck at 100%.

Both claude.ai and Claude Code show that my current weekly usage for all models is 100%, even though my organization admin confirmed there has been no actual usage from my account after June 24.

The issue has persisted across multiple weekly reset cycles.

On July 8, I tried sending a single test message in claude.ai, but it was blocked with the following warning:

"You've reached your Claude message limit. Your limit will reset at 8:40 AM."

My organization admin has verified that my Premium seat is properly assigned, there are no user-level spend limits, there are no organization-level spend limit or usage credit issues, and other users in the same organization are not affected.

Claude Code /status also confirms that I am using the correct Team organization context.

What Should Happen?

The weekly usage counter should reset after the applicable weekly reset cycle.

Since there has been no actual usage from my account after June 24, the weekly usage should no longer show 100%.

I should be able to send messages in claude.ai and use Claude Code under my Team Premium seat allowance.

Error Messages/Logs

claude.ai warning shown when trying to send a test message on July 8:

"You've reached your Claude message limit. Your limit will reset at 8:40 AM."

Claude Code /cost:

Current session: 0% used
Current week (all models): 100% used

Steps to Reproduce

  1. Use a Claude Team Premium account.
  2. Confirm in Claude Code /status that the account is using the Team organization context.
  3. Confirm that the account has a Premium seat assigned and is not Unassigned.
  4. Confirm that there are no user-level spend limits.
  5. Confirm that there are no organization-level usage credit or spend limit issues.
  6. Confirm from admin Usage Analytics that there has been no actual usage after June 24.
  7. Open claude.ai or Claude Code /cost.
  8. Observe that Current week (all models) still shows 100% used.
  9. Try sending a single test message in claude.ai.
  10. Observe that the message is blocked due to the Claude message limit.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.172

Platform

Other

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

Verified facts:

  • Plan: Claude Team
  • Seat type: Premium
  • Claude Code version: 2.1.172
  • Platform: macOS
  • Login method: Claude Team account
  • Organization context in Claude Code: correct Team organization
  • Organization context in claude.ai: correct Team organization
  • Model: opus (claude-opus-4-8)

Admin-confirmed facts:

  • The account is properly assigned to a Premium seat.
  • The seat is not Unassigned.
  • There is no user-level spend limit.
  • There are no organization-level usage credit or spend limit issues.
  • There are no organization-wide monthly spend limit issues.
  • There are no Premium seat-tier restrictions.
  • Usage Analytics shows no actual usage from this account after June 24.
  • Other users in the same organization are not affected.

This appears to be an account-specific issue with the weekly usage counter, Premium seat entitlement state, or usage synchronization between claude.ai and Claude Code.

I also reported this through the Claude support chatbot. The chatbot indicated that, after all standard admin-side causes were ruled out, this appears to be an account-specific technical issue with the usage counter state.

<img width="1490" height="880" alt="Image" src="https://github.com/user-attachments/assets/9d1d61b3-6d3f-4eff-8381-3781ddf71963" />
<img width="1490" height="880" alt="Image" src="https://github.com/user-attachments/assets/8b6387e3-f045-4ba5-953a-b4a3e489b270" />
<img width="1490" height="880" alt="Image" src="https://github.com/user-attachments/assets/e1027282-5af2-47ba-90ec-727115921696" />
<img width="1490" height="880" alt="Image" src="https://github.com/user-attachments/assets/1f0ae7ca-071f-49bb-8634-667bc2723c2c" />

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗