
Codex CLI 0.154.0: Idle CPU Spikes and Accessibility Bugs
This episode breaks down how Codex CLI version 0.154.0 can drive high idle CPU, cause cursor flicker, and disrupt screen readers with nonstop TUI redraws and sparkle animations. It also covers practical workarounds in config and on the command line, plus a few version caveats to watch for.
Show Notes
- macOS VoiceOver regression in 0.154.0: repeated output fragments ...: https://github.com/openai/codex/issues/44728
Chapter 1
Tipping Point: How TUI Animations Spike Idle CPU and Break Accessibility in Version 0.154.0
Ethan Park
Quick shoutout to Jellypod for supporting our daily show . Now, if you updated Codex CLI to version 0.154.0 recently, you, uh, you might have noticed your laptop fan kicking into overdrive for no obvious reason.
Maya
Oh yeah . I thought my terminal was running a heavy build in the background, but my machine was basically idle.
Ethan Park
That is the thing! Current community reports trace that idle load directly to a status indicator in the TUI that schedules redraws about every 32 milliseconds. That is around 31 frames per second, constantly, even when Codex is just waiting on a background task.
Maya
Wait, 31 frames per second ? In a text terminal?
Ethan Park
Right! And that loop alone can consume up to 30 percent CPU on the codex main process. Just standing by.
Maya
That is wild . And, and, and it gets worse than just CPU usage. The update also added a sparkle effect for the new GPT 6 Astra model. Users on GitHub reported that those continuous star animations cause the cursor to jump wildly around the input area, and it completely broke mouse text selection in terminal emulators like Kitty and Ptyxis.
Ethan Park
Ugh , cursor jumping while trying to type a prompt sounds infuriating.
Maya
It really is . But the most severe side effect was for screen reader users. Accessibility reports showed that on macOS VoiceOver, those non stop redraws caused VoiceOver to repeatedly announce tiny fragments of terminal output over and over. It made the tool completely unusable until animations were turned off. One user noted that disabling terminal animations alone restores usability on the updated version.
Ethan Park
Man . That really highlights a fundamental breakdown in how CLI rendering should work. Terminal emulators are designed for streaming plain text as it arrives. When you start running a full graphical render loop in a terminal, polling faster than a display even updates, you flood the terminal buffer with ANSI escape sequences. You end up with massive terminal writes and crazy tmux history bloat.
Maya
I actually ran into that exact tmux issue last night ! I was running a long test suite in tmux, and the tab title spinner was updating so fast that the entire pane buffer started lagging behind my keystrokes. I thought I was losing my mind.
Ethan Park
It is just way too much redraw churn for what is supposed to be a lightweight command line helper.
Chapter 2
Taming the TUI: Config Workarounds, Command Line Overrides, and Known Version 0.154.0 Caveats
Maya
So , if you are dealing with screen flicker, high CPU, or accessibility issues right now, what is the fix?
Ethan Park
Well, thankfully there are a few config toggles you can set in your configuration file, inside your home dot codex directory.
Maya
Right. In your config dot toml file, you want to find or create a single tui section header. Inside that block, you set animations equals false, whimsy equals false, and terminal title equals project in quotes inside brackets. Setting whimsy equals false turns off the Astra sparkle effect specifically. In fact, one tester confirmed that reopening the same conversation with tui dot whimsy equals false greatly reduced the cursor flicker frequency.
Ethan Park
And if you do not want to edit your global configuration file permanently, you can pass a flag on the command line . Just launch with codex space minus c space tui dot animations equals false. That works great for a quick temporary session.
Maya
Just a quick warning on editing the TOML file directly, though . Do not accidentally add a second tui table header if one is already there. Duplicate section headers will cause Codex to completely reject your config file on startup.
Ethan Park
Good catch. Also, keep in mind that changing the config file does not affect an active session retroactively. You have to do a full process restart for the new TUI settings to take effect.
Maya
Oh, and while we are talking about caveats in version 0.154.0, there is another bug to watch out for . The slash rename command is currently broken. If you try to rename an active thread, it silently fails and logs an os error 2 behind the scenes. So do not be surprised if your session name refuses to change.
Ethan Park
It really makes you step back and think . As terminal AI agents get more advanced, teams keep adding visual polish like shimmer effects, spinners, and sparkles. But in a terminal, performance and accessibility have to come first.
Maya
100 percent . Do you think CLI frameworks should just stick to plain text by default and make graphic animations opt in?
Ethan Park
I really do . Save the machine cycles for the actual AI reasoning, not the sparkle effects. That is all for today's quick take, talk soon everyone!
Maya
Bye everyone !