openai / openai/codex

ChatGPT Codex App - no context usage indicator even if Settings -> Show context window usage is on

Open
#43,511 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug context
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

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

26.901.51231

What subscription do you have?

Pro

What platform is your computer?

Darwin 25.6.0 arm64 arm

What issue are you seeing?

There is no context donut indicator (or any indication of the context usage for the current chat, not even with /status), even if the Settings -> Show context window usage switch is on.

What steps can reproduce the bug?

Go to Settings and turn "Show context window usage" on.
Start a new conversation with new chat, or continue an old one.
Observe the fact that there is no context indicator usage for the chat anywhere in the UI.
Weep.

What is the expected behavior?

We should see the context indicator usage for our chats somewhere in the app UI. I'm not picky, experiment all you want. But show it. I was under the impression that enabling "Show context window usage" showed the context window usage indicator, but that is not obviously the case. Consider the fact that people are actually paying to work with your apps, and can't lose their context window usage indicator every other release just because you didn't decide where to render it. That's an important part of the application, it's not ornamental. Please write some regression tests and have them fail when the context window usage indicator doesn't show in the app UI. Make Codex write them maybe.

Additional information

We really would like to see a context window usage indicator attached to all our chats, so we can understand how much context window usage we used so far.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in the Codex App with Settings → Show context window usage enabled, then trace the desktop UI path that renders chat status. Done means every chat visibly shows context usage and regression tests fail when the indicator is absent; no specific files or existing tests are named in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, rust
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.