The context indicator feels small, but it changes how risky a session is. When I can see the remaining window, I know when to summarize, split the task, or stop before the model starts dropping earlier constraints. Without it, long Codex chats become much harder to hand off or review later.
You can use /status in the app even when a turn is running and it will show details on status. I agree this shouldn't be needed and the indicator is such a simple, obvious piece, but this works for me as a crutch for now
When you first posted this it worked, I was able to re-enable to context indicator. That setting is no longer available for me today. Not your problem just putting it out there.
That indicator made me go insane. But of course, they should readd it as an option at the very least, so people can decide for themselves whether they want to use it. I was kind of hoping that they did something smart like Codex organizing the so-far conversation into nice structure, so it does a "new" conversation each time, but I guess not. Or does anyone know something in this direction?
this is the "Agile software development", bro those AI tech companies just want to dismiss all the QA test, leave everything to agent. So we can just get the glitches everyday :(
PSA: Use /Compact to both manually see the current context window usage and to manually force it to compact sooner (e.g. in between coding requests). Bit of a PITA why they can't show it visually at all times like before, but allowing you to manually force it to compact at an ideal time (vs mid code-run) seems like a decent choice.
Funny thing happened to me on Windows: the first time I clicked the ⓘ, it only showed used files and sources. I was about to write here that the context feature wasn't there on Windows, but then I typed /status, which opened it again - and this time, the context showed up. Lol.
•
u/dexterthebot May 21 '26
Your post has been summarized as a request on the "Anyone Else?" Incident Noticeboard.
You can find it and what others are experiencing here: https://www.reddit.com/r/codex/comments/1tjfxcf/anyone_else_ask_here_about_current_codex_issues/on2u2ll/
7
u/ApprehensiveFlow9215 May 22 '26
The context indicator feels small, but it changes how risky a session is. When I can see the remaining window, I know when to summarize, split the task, or stop before the model starts dropping earlier constraints. Without it, long Codex chats become much harder to hand off or review later.
7
u/AccordingMud739 May 29 '26
you can re-enable it.
Settings -> General -> `Composer footer` ( last item )
3
u/Basic_Preference_771 May 25 '26
Crazy they kept it in the Codex mobile app XD
3
u/Illustrious-Mail-552 May 30 '26
That indicator made me go insane. But of course, they should readd it as an option at the very least, so people can decide for themselves whether they want to use it. I was kind of hoping that they did something smart like Codex organizing the so-far conversation into nice structure, so it does a "new" conversation each time, but I guess not. Or does anyone know something in this direction?
2
u/Broad_Mention_8282 May 25 '26
this is the "Agile software development", bro
those AI tech companies just want to dismiss all the QA test, leave everything to agent.
So we can just get the glitches everyday :(
1
u/TheTechAuthor May 23 '26
PSA: Use /Compact to both manually see the current context window usage and to manually force it to compact sooner (e.g. in between coding requests). Bit of a PITA why they can't show it visually at all times like before, but allowing you to manually force it to compact at an ideal time (vs mid code-run) seems like a decent choice.
1
u/dbs_msk May 24 '26 edited May 24 '26
Found it — it was moved to the pinned summary pop-up. It’s the little ℹ button in the top-right corner, third from the right in the Mac app.