Still working, but no still working / progress indication, making it look finished/idle

What version of Codex is running?

0.93.0

What subscription do you have?

pro

Which model were you using?

gpt-5.2 (high)

What platform is your computer?

Linux 6.18.6-arch1-1 x86_64 unknown

What terminal emulator and version are you using (if applicable)?

n/a

What issue are you seeing?

During an active Codex CLI run, the CLI occasionally continues making progress (eventually produces the final response/output), but the UI stops indicating it’s still working. From the user’s perspective it looks like Codex is done or idle, even though it is still processing.

What steps can reproduce the bug?

Uploaded thread: 019c249c-b026-7a71-bf0e-7c5bc54ddb49

I haven't figured out the trigger. It happened in the upload thread id after I sent "I can't even drag the window around. I assumed this was a browseros/chromium issue, but maybe KDE is involved too somehow. The rest of KDE is fine." around 13:15:50 Eastern, until it gave a response around 1:17:07 Eastern, without me giving any more input.

What is the expected behavior?

While Codex is still processing, the CLI should continuously display a clear “working” indicator (say "Thinking", show a spinner/status line/progress state) or otherwise make it obvious that the run is still active until completion (or a clear error/timeout).

It often does this, but it often doesn't.

Additional information

• This is not a hang: Codex eventually completes successfully.
• The problem is primarily UX/state signaling: the CLI looks finished/idle while still running.
• Often it will show a response like "... do you want me to do x?" and it looks to me like it's asking me, but Codex CLI will proceed from there.