Show Notes
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
More from The Codex Changelog
A closed background-compaction channel could leave a Codex app-server turn stuck in progress; learn the reported recovery steps and the fix associated with PR 55581, whose release availability is still unclear. We also cover an open report of queued input disappearing when pre-turn compaction is interrupted, plus notes on CLI voice disconnects, installer download-host selection, and GPT 5.5 retirement.
Codex’s new PromptCacheKey policy lets hosts keep session identity separate from prompt-cache routing. Learn how to choose a shared key for parallel subagents, omit the field for compatible gateways, and reapply the policy when resuming threads—plus caveats for cache hits and prompt consistency. Also: updates to fork-prefix preservation, authentication errors, Guardian metrics, and compaction recovery.
Codex 0.164.0 alpha adds a startup check for feature-flag mismatches between the CLI and its background daemon, replacing a silent fallback to embedded mode with a recovery prompt. Learn how to configure feature overrides and reconnect safely, including the warning that restarting a shared daemon can interrupt active subagents; the episode also covers improvements to TUI question rendering, picker ranking, remote reconnects, and Linux launcher security.
Codex’s new PreModelRequest and PostModelRequest hooks expose model-call lifecycle data, including retries, status, and reported token usage. Learn how to register an async logging hook, account for cancelled turns, and check build availability, plus smaller security and workflow updates.
An open bug report for Codex 0.163.0 describes sessions stuck on “Waiting for startup” when an unused provider’s command-based auth table omits cwd and the daemon’s startup directory has been deleted. Learn how to spot the risky config, choose a durable explicit cwd, and recover a stuck session; the episode also covers a prerelease terminal-input stall, a WSL2 resume workaround, and the new /side command.