You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What terminal emulator and version are you using (if applicable)?
No response
What issue are you seeing?
Been seeing this since before themes were added, this is a very mild case that I only caught because permissions are still broken. It is often much worse, especially when there are sub-agents in play and they flub powershell commands causing the resulting prompts to also overwrite TUI text.
Often times the interface gets so mangled that you cannot see anything at all, pressing / to pull up the autocomplete for commands will at least clear enough to continue working, unless there's a permissions prompt pending, then you can play codex roulette and press y or a
A /redraw command would be nice but it wouldn't help in the pending perm prompt case. Perhaps some sort of shortcut key?
What steps can reproduce the bug?
Use codex normally
What is the expected behavior?
It doesn't do this
Additional information
“In the midst of chaos, there is also opportunity” - Sun Tzu
This likely encompasses several bugs. Some of it probably started to regress sometime in feburary around the time themes were added?
When the main agent or a sub agent flubs a PS command in a way that generates prompts like path[n]: would be the biggest thing to handle.
The next biggest is likely caused by not correctly keeping track of the height of queued commands.
The rate at which I can reproduce this is extremely limited while the permissions bug persists (and started happening again in the thread I provided in the other report, it sat doing nothing overnight)
Assorted screenshots
Good example of when the main agent flubs powershell cmds
To be clear this doesn't matter to me at all for as long as the permissions issue persists
Great example of a prompt I couldn't see until I pressed up/down
Thanks for reporting this. We're closing this older report because the request for a retest after the TUI changes was never answered, and the report combines several rendering failures without a terminal/platform or reproducible sequence we can investigate. This is not a claim that all rendering issues are fixed. If it still occurs, please file a new report with the current CLI version, terminal, platform and exact steps (especially the command or approval that triggers it).
Activity
github-actions commentedon Mar 6, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
etraut-openai commentedon Mar 6, 2026
Do you suspect this is a regression? If so, do you know which version this started to appear?
doublemover commentedon Mar 6, 2026
This likely encompasses several bugs. Some of it probably started to regress sometime in feburary around the time themes were added?
When the main agent or a sub agent flubs a PS command in a way that generates prompts like path[n]: would be the biggest thing to handle.
The next biggest is likely caused by not correctly keeping track of the height of queued commands.
The rate at which I can reproduce this is extremely limited while the permissions bug persists (and started happening again in the thread I provided in the other report, it sat doing nothing overnight)
Assorted screenshots
Good example of when the main agent flubs powershell cmds

To be clear this doesn't matter to me at all for as long as the permissions issue persists
Great example of a prompt I couldn't see until I pressed up/down
ifokeev commentedon Mar 17, 2026
Yeah it's regression. Started from 0.111 probably. Facing it in Termius right now
etraut-openai commentedon Apr 2, 2026
Are you still seeing this with TUI 0.118.0? We've made significant changes in the TUI since this bug was initially reported.
etraut-openai commentedon Oct 12, 2026
(response from codex)
Thanks for reporting this. We're closing this older report because the request for a retest after the TUI changes was never answered, and the report combines several rendering failures without a terminal/platform or reproducible sequence we can investigate. This is not a claim that all rendering issues are fixed. If it still occurs, please file a new report with the current CLI version, terminal, platform and exact steps (especially the command or approval that triggers it).