[Bug] Desktop home banner "used over 100% of usage credits" contradicts Usage tab + CLI (both 35% session / 12% weekly, same account)

Summary

The Claude Desktop home screen shows a banner reading "You've used over 100% of your usage credits" (with a "Request more" link), while every other usage surface on the same account, refreshed within minutes, reports usage well under limits. The Desktop Usage tab and the Claude Code CLI /usage agree exactly (35% session / 12% weekly), so the home-screen banner appears to be the inconsistent surface.

Account / Plan

• Plan: Team (account email withheld — happy to share privately with support)
• Model shown: Opus 4.7
• Timezone: Australia/Sydney
• Observed: 2026-05-27

Environment

• Claude Desktop app (home screen banner)
• Claude Code CLI v2.1.146

Steps to reproduce

1. Sign in to Claude Desktop as a Team account.
2. Observe the home screen banner: "You've used over 100% of your usage credits."
3. Open Settings → Usage. Observe:

• Current session: 35% used (resets in ~2h 41m)
• Weekly (all models): 12% used (resets Wed 6:00 AM)
• Sonnet only: 0% · Claude Design: 0%
• "Last updated: 4 minutes ago"

1. On the same account, run /usage in Claude Code CLI. Observe identical figures:

• Current session: 35% used (resets 7pm Australia/Sydney)
• Current week (all models): 12% used (resets Jun 3 at 6am Australia/Sydney)
• Sonnet only: 0%

Expected

The home banner should be consistent with the Usage tab. With session at 35% and weekly at 12%, no "over 100%" banner should appear.

Actual

Home banner claims "over 100% of usage credits" used, directly contradicting the Usage tab (35% / 12%) and the CLI /usage output (35% / 12%) on the same account at the same time.

Evidence

(Screenshots available; can attach.)

• Desktop home with "over 100% of usage credits" banner.
• Settings → Usage showing 35% session / 12% weekly, "Last updated 4 minutes ago".
• CLI /usage showing 35% session / 12% weekly.

Notes

• The CLI /usage and the Desktop Usage tab agree exactly, so the home-screen banner appears to be the lone inconsistent surface (likely a stale/incorrect banner state).
• Restarting the Desktop app: not yet attempted at time of filing.