Claude in Chrome shows '5-hour limit reached' when actual usage is only 8% session/52% weekly (Pro plan)

Bug Description:
Claude in Chrome extension is incorrectly reporting that I've hit my 5-hour session limit when my actual usage statistics show I have plenty of capacity remaining.
Steps to Reproduce:

Open Claude in Chrome extension (Pro plan subscriber)
Use the extension for approximately 1 hour of browsing/interaction
Extension displays: "5-hour limit reached · resets 12:00 AM · Subscribe to Max"

Expected Behavior:
Extension should allow continued use until actual session or weekly limits are reached, as shown in the usage dashboard.
Actual Behavior:
Extension blocks further use claiming 5-hour limit is reached, despite actual usage showing significant remaining capacity.
Evidence of Discrepancy:
At the time of the "limit reached" message, running /usage in Claude Code (VS Code extension) showed:

Session (5hr): 8% used, resets in 4h
Weekly (7 day): 52% used, resets in 1d

This means I had:

92% of my 5-hour session remaining
48% of my weekly quota remaining

Environment:

Plan: Claude Pro
Chrome extension: Latest version
Also using: Claude Code in VS Code (same window session)
OS: Windows

Additional Context:
According to documentation, usage limits should be shared across all Claude interfaces (claude.ai, Claude Code, Chrome extension). However, the Chrome extension appears to be either:

Miscalculating usage internally
Applying an undocumented stricter limit for Pro users in Chrome
Not properly syncing with the actual usage tracking system

This makes the Chrome extension effectively unusable despite having ample quota available on my Pro plan.

!Image