Regression: context usage percentage is missing from Codex input composer

Resolved 💬 3 comments Opened May 22, 2026 by JavierPiedra Closed May 22, 2026

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

26.519.31651

What subscription do you have?

Pro

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

The Codex app no longer shows the context usage percentage in the input composer.

Previously, the input area showed the current context usage percentage, which made it possible to tell when a conversation was getting close to the context limit. That signal is important during long coding sessions because it helps decide when to summarize, split work into a new thread, or avoid starting a large task right before context pressure becomes a problem.

Actual behavior:

  • The input composer no longer shows the context usage percentage.
  • I do not see an equivalent visible context usage indicator elsewhere in the main chat UI.

Expected behavior:

  • The Codex app should continue showing the current context usage percentage in or near the input composer, or provide an equally visible replacement.
  • The indicator should be available without needing to open a separate debug view or infer context pressure from behavior.

Why this matters:

  • Long-running coding sessions depend on knowing when the thread is approaching the context limit.
  • Without the percentage, users have less control over when to checkpoint, summarize, or start a new conversation.
  • This increases the chance of context loss or degraded task continuity.

This looks like a UI regression from the previous Codex app behavior.

What steps can reproduce the bug?

Open codex app
open a new conversation
look for progress chart

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗