Windows Desktop context usage donut shows 0% on initial thread load after reopening the app, then recovers after sending a message

What version of the Codex App are you using (From “About Codex” dialog)?

26.616.51431

What subscription do you have?

Pro

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What issue are you seeing?

For existing threads, the context usage donut in Codex Desktop shows 0% when the thread is first opened after reopening the app.

This appears to be incorrect, because those threads are already long-running and clearly should not have zero context usage.

If I send one new message in the thread, the donut then refreshes and starts showing a non-zero value again.

So this does not look like the actual thread context is empty. It looks more like the UI is failing to load or hydrate the context usage indicator on first render, and only recalculates it after a new turn is sent.

What actually happened?

On initial thread load after reopening the app, the donut shows 0%.

After sending a new message, the usage indicator refreshes and shows a more plausible non-zero value.

Additional context

A few observations that may help:

• I first noticed this after the computer slept and resumed, but I later restarted the computer and reopened Codex Desktop, and the same behavior still happened.
• So the trigger does not seem limited to sleep/wake with Codex left open. Reopening the app also appears sufficient.
• The same behavior can happen across multiple existing threads, not just one.
• The thread content itself does not appear to be gone; the issue seems specific to the usage indicator UI/state on initial load.
• My current hypothesis is that the context usage state is not being refreshed correctly when an existing thread is first loaded, so the donut renders 0% until a new message triggers a second refresh.

This looks like a UI/state refresh bug rather than a true context reset.

What steps can reproduce the bug?

Open Codex Desktop on Windows.
Work in one or more threads until they clearly have non-trivial context usage.
Close Codex Desktop, or restart the computer and reopen Codex Desktop.
Open one of those existing threads.
Observe that the context usage donut shows 0% on initial load.
Send one new message in that thread.
Observe that the donut now refreshes and shows a non-zero value again.

What is the expected behavior?

The context usage donut should show the correct current usage immediately when the thread is opened.

It should not display 0% as a placeholder if the thread already has meaningful context usage.

Additional information

_No response_