codex - 💡(How to fix) Fix New Codex version makes task execution completely opaque

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

recently

What subscription do you have?

plus

What platform is your computer?

macos

What issue are you seeing?

Description

In the new version of Codex, task execution has become extremely opaque. Compared with previous versions, Codex now often just stays in a “thinking” state for a long time, without showing whether it is actually doing anything.

As a user, I cannot tell whether Codex is reading files, editing code, running commands, making progress, or simply stuck.

Previous versions felt much better in this regard. Even if the task took some time, there was at least some sense that Codex was actively working. In the current version, the lack of visibility makes the experience feel like a complete black box.

Current behavior

Codex frequently:

• Shows “thinking” for a long time
• Provides no intermediate progress updates
• Does not show whether it is reading files, editing code, or running commands
• Gives no indication of whether it is stuck
• Leaves the user passively waiting with no useful feedback

This is especially frustrating when working on larger codebases or more complex tasks, where execution can naturally take longer.

Expected behavior

Codex should provide clearer feedback during task execution, such as:

• Showing what it is currently doing
• Indicating when it is reading files, editing code, or running commands
• Providing periodic progress updates during long tasks
• Making it easier to tell whether the task is still progressing or has stalled
• Restoring the more transparent execution feedback that older versions had

Why this matters

A major part of the value of Codex is that users can trust it to perform coding tasks reliably. But when the execution process is completely hidden, it becomes very difficult to trust whether anything is actually happening.

The current experience constantly makes me wonder:

Is Codex still working, or is it stuck?

That uncertainty is extremely frustrating and makes the new version feel like a regression in usability compared with earlier versions.

Please consider improving the visibility of Codex’s execution process so users can understand what Codex is currently doing and whether the task is still making progress.

<img width="378" height="214" alt="Image" src="https://github.com/user-attachments/assets/05d4300f-8344-41eb-a759-6dc5f3a37f74" />

What steps can reproduce the bug?

recently version

What is the expected behavior?

No response

Additional information

No response