Codex Desktop no longer shows visible context/token usage indicator

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

26.519.2081.0

What subscription do you have?

ChatGPT Business

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

After updating Codex Desktop, the app no longer shows a visible context/token usage indicator in the chat UI.

Previously, Codex exposed context usage information such as context-window pressure near the input area / usage indicator. After the recent update, I can no longer find this context usage display or tooltip.

This makes long coding sessions harder to manage because I cannot tell when a thread is getting close to compaction, context pressure, or possible context loss. For professional coding workflows, this information is important because it helps users decide when to compact, start a new thread, reduce pasted context, or split work.

Related existing issues:

What steps can reproduce the bug?

Open Codex Desktop on Windows.
Start or open any Codex chat/thread.
Look near the input area or usage/context indicator where context usage was previously visible.
Hover over available usage/status UI elements.
Observe that there is no visible context/token usage information or context pressure indicator.

What is the expected behavior?

Codex Desktop should show visible context/token usage information again, or provide an advanced context/status panel.

Ideally it should show:

current context
remaining context or approximate context pressure
whether compaction has happened or is approaching
a clear distinction between current context usage and cumulative usage/quota

Additional information

This appears to be a UI/UX regression. If a raw percentage is considered misleading, an approximate context health indicator would still be much better than hiding the information entirely.

Suggested UI:

Low / Medium / High context pressure
Last compaction status
Loaded files or active context sources
“Consider starting a new thread” recommendation when appropriate

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

Powered by Codex Action

I can confirm the context window indicator has gone.

again, a stupid bug that can reproduce if you just open app

Additional local evidence for the context/token usage indicator regression:

Environment:

Windows x64, zh-CN UI.
Current Desktop package path: C:\Program Files\WindowsApps\OpenAI.Codex_26.519.2081.0_x64__2p2nqsd0c76g0\app\Codex.exe
Crashpad annotation reports app version 26.519.21041.
Previous session where the indicator reappeared was observed on 26.513.4821.0; after reboot only 26.519.2081.0 is installed/running.

Config/backend evidence:

models_cache.json did not regress: gpt-5.5.effective_context_window_percent=95, context_window=272000; gpt-5.4.context_window=1050000, effective_context_window_percent=95 via a local model catalog.
The active thread continues to emit token_count events with model_context_window=258400 for gpt-5.5.
Auto-compaction is working; the UI shows an in-thread context compacted separator after compaction.

Frontend evidence from the extracted 26.519 webview bundle:

git-branch-picker-dropdown-content-DbCczbcx.js computes context usage from tokenUsage.modelContextWindow and tokenUsage.last.totalTokens.
In composer-CWBCSPDQ.js, that computed usage is only referenced by:
- the /compact slash-command description: Compact this thread's context ({usage}% full)
- the /status panel row: Context: {remaining}% left ({used} used / {total})
There is no persistent composer/footer context indicator in the current 26.519 bundle. A screenshot of the current UI also shows no persistent context/token usage indicator near the composer, only the model selector and the compacted-context separator in the transcript.

This suggests the current issue is not a model metadata or auto-compaction failure. The backend has the required token/context data, but the Desktop UI no longer exposes it as a visible persistent context indicator in 26.519.

Adding another data point from #23838, which was closed as a duplicate of this issue.

This is specifically about the Codex desktop app, not the CLI/TUI /statusline feature. /status is useful as an explicit command, but it is not a replacement for passive context awareness during long-running desktop threads.

The use case is not just curiosity about token counts. A persistent, clearly labeled Context N% used or Context N% remaining indicator helps users decide when to compact, fork, or start a fresh thread before output quality starts degrading or auto-compaction surprises them. The previous passive indicator materially affected workflow planning in long sessions.

If the old UI caused confusion with quota/rate limits, an opt-in advanced setting would solve that without removing the signal entirely:

Label it as conversation context, not quota or rate-limit usage.
Keep it visually separate from 5-hour / weekly usage.
Allow users to hide it by default if the goal is a simpler main UI.

I also submitted this through the Codex feedback form: 019e48ff-3e50-7750-87c8-4d29a4fd0ab8.

again, a stupid bug that can reproduce if you just open app

Yes, they are very stupid. Every update has very stupid bugs, and the bugs in the Codex app are outrageously numerous.

Same issue. Please fix quickly.

I can confirm the context window indicator has gone.

I'm on a MacOS 15.7.7 (24G720). It's missing in Version 26.519.22136 (3003) here too. It was visible in the previous release.

Daily reminder that we miss our context window indicator.

Daily reminder that we miss our context window indicator.

Any idea how to get this back? It's breaking my workflow. Is this truly the intention of the Codex team? I can't believe that.

We received your feedback about the current solution not working well for vertical/portrait monitor setups. That's a good point that we didn't fully appreciate when we made the recent change.

It's a three-day weekend in the U.S., and most of the Codex team is taking the weekend off to spend time with their friends and families, but we'll pick this up again early next week. Your feedback isn't going unheard!

Thank you so much for listening to the community feedback! It is absolutely amazing to see this feature come back better and more optimized than ever. We truly appreciate your dedication and hard work!

It's in General Settings, at the bottom. "Composer Footer"

Ty @v3i1y cc: @SergeNS-mne

When I open Settings> General, the last thing I see is "Code Review" and I don't see this option anywhere

Well, now I honestly do not know whether to laugh or cry.

Yes, I found the setting and enabled the old compact indicator. Thank you for pointing out that it is under General Settings → Composer Footer.

But the funny part is that I would never have discovered this without first posting a frustrated complaint in this thread. So apparently this was a blessing in disguise: the bad UX forced me to complain, and the complaint finally led me to the hidden setting that fixes the bad UX.

That said, this also shows the remaining problem very clearly. If a workflow-critical indicator is restored, users should not have to discover it through GitHub comments after getting angry enough to complain. It should be obvious in the app, mentioned in the release notes, or surfaced directly when /status is used.

The feature is back, and that is genuinely good. But the path to finding it was unnecessarily painful.

Exactly what i was going to say.

We also lost the 1M Context Window: #24031
And even "copy to markdown" button has disappeared: #25201

Idk what the fuck is happening at OpenAI or the Codex team but i'm thinking more and more about going all in on Claude at this rate.

@etraut-openai

For VS Code users, rollback from v26.519.32039 to v26.513.21555 to get the visible context/token usage indicator back as a short-term workaround to stay productive for now.

Extensions -> Codex -> Uninstall (drop-down arrow) -> Install Specific Version -> 26.513.21555 (1 wk ago)

For the latest Codex VS Code extension (v26.601.21317), I don't see any way to toggle "Show context window usage" like in the Codex app. The only way for me to get the token usage donut is to downgrade to v26.513.21555.

@etraut-openai was this setting only added to the Codex app, and not the VS Code extension?

Available settings:

Composer Footer on v26.601.21317 (latest version, no token usage donut):

Composer footer on v26.513.21555 (last version with token usage donut):

@tomvothecoder

@tomvothecoder, that setting is included in the latest version of the IDE Extension. Click on the gear icon in the Codex side panel, and choose "Codex settings".

@etraut-openai

@etraut-openai Great, thanks for the quick reply. I appreciate you and the team for restoring this feature.

@etraut-openai

@etraut-openai what about the dial that was located in the top-right corner of the screen, the one showing the actual number of tokens consumed by the session? It used to be where the arrow in the screenshot is pointing

That is gone too. Are you planning to bring it back? Should I open another issue?

@AndreaPi

@AndreaPi, we temporarily moved the dial (aka donut) to that location, but we moved it back to the composer based on community feedback. You can still see the details by hovering over the donut indicator.

Yes google searcher, this is solved

To save you time (and reading drama): toggle this on in the Codex settings like so.
Codex app version: 26.602.30954

Screencast.From.2026-06-05.12-31-44.mp4

A bit of help, here? I read just above that issue is solved in 26.602.30954, but I can't manage to find de settings to put back in display the left quota. This info is really important for me... Codex just threw at me the "no more quota" without any warning, I hate that, we were in the middle of something..

It was not showing for me too
I saw this new setting which when enabled, shows the context status ring back

And still suffering at 250k - 50k sys prompt - 50k overhead context window which is 150k effective, vs what we had with 5.4 was 1050k-50k-50k=950k effective. which is over 5x worse. id rather the 1m context EVEN at 4x pricing.

For those experiencing the lack of logged in info issue:

Make sure you update to the latest version of Codex. After doing so, you should have a 'Log Out' option. Log out. Log in using your ChatGPT account creds. This fixed the issue for me.

Trillion dollar company that makes state of the art AI models but can't write the code to keep a fucking partially filled circle sitting in a docked bar. If you don't read this as a "fuck you" to you from OpenAI, you're reading it wrong.

Same problem. I can't believe the way that every time you update this application you introduce bugs that would have been found if you were actually using your own application.

Navigation Menu

Repository navigation

Codex Desktop no longer shows visible context/token usage indicator #23794

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

What subscription do you have?

What platform is your computer?

What issue are you seeing?

What steps can reproduce the bug?

What is the expected behavior?

Additional information

158 remaining items

Yes google searcher, this is solved

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Codex Desktop no longer shows visible context/token usage indicator #23794

Description

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

What subscription do you have?

What platform is your computer?

What issue are you seeing?

What steps can reproduce the bug?

What is the expected behavior?

Additional information

Activity

github-actions commented on May 21, 2026

MeXenon commented on May 21, 2026

mrbeardad commented on May 21, 2026

dushengyi1993 commented on May 21, 2026

tim-osterhus commented on May 21, 2026

s7monk commented on May 21, 2026

NeonHazeGameStudio commented on May 21, 2026

alissonsfeliciano commented on May 21, 2026

DanKaplanSES commented on May 21, 2026

Statusnone420 commented on May 21, 2026

NN1985 commented on May 21, 2026

158 remaining items

cooltzy commented on May 31, 2026

paulreichling commented on May 31, 2026

VolkumDev commented on Jun 1, 2026

tomvothecoder commented on Jun 3, 2026

etraut-openai commented on Jun 3, 2026

tomvothecoder commented on Jun 3, 2026

AndreaPi commented on Jun 5, 2026

etraut-openai commented on Jun 5, 2026

irm-codebase commented on Jun 5, 2026

Yes google searcher, this is solved

djoole commented on Jun 5, 2026

raunaqpatel-cmd commented on Jun 9, 2026

pkkkkkkkkkkkkk commented on Jun 16, 2026

rowenrowen commented on Jun 18, 2026

planetzalex commented on Jun 28, 2026

Promethean-Pty-Ltd commented on Jul 16, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions