Desktop app: context indicator does not report the current chat after switching chats or before the first message

Summary

In the Windows desktop client, the round context indicator does not report the context of the chat that is currently open. Two situations where the number shown is not this chat's context:

1. Right after switching between chats, the indicator keeps a value that does not belong to the newly opened chat.
2. Before the first action in a chat, no per-chat context figure is shown at all.

Because the same control also carries rate-limit information, the percentage on screen can belong to a different counter entirely (five-hour limit, weekly limit, or context window), and there is no way to tell which one is being displayed at a glance.

Steps to reproduce

1. Open a chat with a long transcript and let its context grow.
2. Switch to a different chat.
3. Look at the round indicator before sending anything in the new chat.

Expected behaviour

The indicator reports the context window of the chat that is currently open, and the counter it represents is identifiable.

Actual behaviour

The value shown does not correspond to the open chat. It appears to reflect whichever counter is highest at that moment, without distinguishing the context window from the five-hour or weekly limits.

Why this matters

A user who relies on this control to decide when to hand off to a fresh chat gets a misleading signal. In our case the context reached 83 percent while the visible indicator suggested there was room, and the handoff was started late as a result.

Environment

• Claude Code desktop app, Code tab
• App version: <fill from Help, About>
• Windows 11 Pro, build 26100
• Plan: Max

Related, for triage context

• #64546, context window display shows a stale count from the previous session on new session start and corrects after the first message. Closed as a duplicate of #60109; the lock bot on that thread asks for a new issue linking back to it, which is why this report is filed separately.
• #60109, /usage session view shows stale or cross-session data. Closed, not planned.
• #49927, usage indicator flickers between different percentages. Closed, not planned.
• #81039, desktop app under-reports the context window. Open.

The part not covered by any of the above is the suspicion that the control renders the maximum of several unrelated counters rather than the context of the current chat.