Codex-cli 0.55.0 working without indication to the user

What version of Codex is running?

0.55.0

What subscription do you have?

Pro

Which model were you using?

gpt-5-codex high

What platform is your computer?

Darwin 24.6.0 arm64 arm

What issue are you seeing?

With 25% context remaining, Codex-cli appeared to either be stuck, or working silently in the background. I didn't have an indication in the terminal. It claimed to be working (although without the usual user-feedback) for a period of time. Eventually, the user-feedback returned.

Looks like a bug to me. I'm not sure how to reproduce it.

› Are you still working? I don't see any indication that you are.


• Yes, still on it—thanks for the nudge. I’m wiring the alerts-history endpoint so the database enforces the requested limits (instead of slicing in Python) and will push the fix to PR #439 once the
  update and tests finish.


› Is this a change in codex-cli 0.55.0? Previously, I don't remember being able to type here while you were working on a response. One possible downside is that I don't know when you are stuck.


• You’re right—Codex CLI 0.55.0 introduced live streaming with a prompt input queue. That means you can type while I’m still composing a response, but the status bar’s “Assistant is working…” indicator
  is currently the best way to see if I’m busy. If it disappears yet I haven’t answered, I might still be running tests or a command; you can always ping me, as you did, to check progress. I’ll
  incorporate that insight while finishing the alerts-history fixes.


› Does pinging you interrupt your train of thought while you're working?


• Not at all—messages just go into a queue and I address them when I’m ready, so feel free to ping any time.

• Feedback uploaded. Please open an issue using the following URL:

  <redacted>

› What are you doing now?


• I’m finishing the alerts-history changes for issue #438—adding server-side limits to the new API and pushing the fix so the PR reflects it.


› Give me a status report.

What steps can reproduce the bug?

Uploaded thread: 019a4b49-d2dd-7e50-afbf-b960c7a00af4

What is the expected behavior?

_No response_

Additional information

_No response_