Reimplement visible context/token usage indicator in Codex Desktop App

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

26.513.40821

What subscription do you have?

Plus

What platform is your computer?

Windows 10 64

What issue are you seeing?

Title: Reimplement visible context/token usage indicator in Codex Desktop App

I’d like to request that Codex Desktop officially restore or re-add a visible context/token usage indicator on mouse-over.

The current desktop app experience makes it difficult to understand how much context is being used, when compaction is likely, and whether a long-running session is approaching a practical context limit. This information is operationally important for coding sessions, especially when working with large repos, long investigations, multi-agent work, or expensive/high-context models.

Codex already appears to track related information internally, including token usage, context window metadata, rate-limit state, and compaction events. The terminal/TUI and local state/telemetry surfaces expose parts of this indirectly, but the desktop app does not provide this anymore when hovering over the usage symnbol.

Requested behavior:

• Show current context/token usage in the Codex Desktop UI.
• Show remaining context or percentage of effective context window used.
• Show when auto-compaction is approaching or has happened.
• Ideally distinguish current-turn/context usage from cumulative thread token usage.
• Make the indicator visible by default or available via a settings toggle.

Why this matters:

• Users need to know when a thread is getting risky before context is lost or summarized.
• Hidden usage makes the app feel less trustworthy, especially for long professional coding sessions.
• It helps users decide when to compact, fork, start a new thread, reduce pasted context, or switch models.
• It aligns the desktop app with the level of observability serious users expect from Codex.

This should be implemented officially in the desktop UI rather than requiring users to inspect local SQLite state, app-server events, telemetry, or terminal-only status lines.

What steps can reproduce the bug?

Feedback ID: 019e42d6-0d47-7e12-bb3d-19af3a966aad

What is the expected behavior?

_No response_

Additional information

This seemingly intentional regression does not exactly instill high confidence in company transparency. :/