/ps not working during a goal
Resolved 💬 5 comments Opened May 17, 2026 by kendonB Closed May 20, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex CLI is running?
0.130.0
What subscription do you have?
Pro
Which model were you using?
gpt-5.5
What platform is your computer?
WSL
What terminal emulator and version are you using (if applicable)?
Windows Terminal
Codex doctor report
What issue are you seeing?
/ps is not working when a background terminal is being used
<img width="795" height="185" alt="Image" src="https://github.com/user-attachments/assets/c4d043a8-0005-4238-bb7c-2e031899a290" />
This happened during a paused goal and a minimal attempt to use /ps in a fresh script worked fine.
What steps can reproduce the bug?
/goal run sleep 20 5 times in a row
then /ps once a background terminal starts
What is the expected behavior?
_No response_
Additional information
_No response_
5 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
not a duplicate
Do you still have that session available? If so, please use
/feedbackand post the session ID here. Without the rollout, I don't think we'll have enough information to diagnose this.I think it's unlikely that this has to do with
/goal, since there's no interaction between that feature and background terminals. We've had reports of background terminals appearing as "stuck", independent of goals. I suspect that's what's happening here.Out of curiosity, have you used
/sideduring this session? There's a possibility that has an interaction with background terminal events.I had used side - but a minimal /side during a simple conversation didn't reproduce it. I have a few conversations open and I can't remember which it was. I will send the chat id if I see it again.
Thanks for the bug report. I think I understand the problem. This will be addressed in the next release.