Codex Desktop 26.623 on macOS: context-window usage indicator missing despite show-context-window-usage=true

Resolved 💬 1 comment Opened Jun 30, 2026 by oorangee97 Closed Jul 11, 2026

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

26.623.70822

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

After the June 28 update, the context-window usage indicator disappeared from the Codex Desktop composer on macOS.

Previously, I could see a small circular context/window usage indicator in the composer footer near the input box. I also previously saw related Settings entries such as “Composer footer” and “Window usage”. In the current app version, the indicator is no longer visible, and those Settings entries are no longer discoverable.

This does not look like I manually disabled it. Local config still contains:

desktop.show-context-window-usage = true

Local token usage events still appear to exist, so this looks like the composer UI / Settings control is hidden or not rendering, rather than token usage tracking being unavailable.

This affects long-running threads because there is no passive way to monitor context pressure before compaction or quality degradation.

What steps can reproduce the bug?

Feedback ID: 019f18e2-b833-7593-ae81-ac95b048ada2

What is the expected behavior?

The context-window usage indicator should remain visible in the composer when show-context-window-usage is enabled.

If the indicator or setting was intentionally moved or removed, the app should provide a visible replacement, migration path, or release-note explanation.

Additional information

Related to #30693, but opening a separate report because this reproduces on macOS 26.623.70822 and includes an additional symptom: the Settings entry/toggle for context-window usage is also no longer visible, while local config still has show-context-window-usage=true.

View original on GitHub ↗

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