`/stop` does not clear background terminals shown by `/ps`

[nbros]

What version of Codex CLI is running?

v0.118.0

What subscription do you have?

Pro

Which model were you using?

gpt-5.4 fast

What platform is your computer?

macOS 26.4

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

Ghostty

What issue are you seeing?

/stop says it stopped all background terminals, but /ps still shows the same zombie terminal afterward.

What steps can reproduce the bug?

1. Ask codex to run a task that creates a background terminal
2. Run /ps
3. Run /stop
4. Run /ps again

The same background terminal is still listed after /stop.

What is the expected behavior?

After /stop, /ps should no longer show that terminal.

Additional information

• Stopping all background terminals.

/ps

Background terminals

  • ls && find . -maxdepth 2 -name '*.csproj' -o -name '*.sln' && dotnet build -nolo [...]

• Stopping all background terminals.

/ps

Background terminals

  • ls && find . -maxdepth 2 -name '*.csproj' -o -name '*.sln' && dotnet build -nolo [...]
```

[github-actions]

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• Codex repeatedly fails to apply patch and keeps spinning background terminals that don't stop running #16311

Powered by Codex Action

[doublemover]

I've had this happen on and off on windows, too. Sometimes the processes were still there, sometimes they weren't (regardless of what /ps said was present or what /stop claimed to do). I got into the habit of closing and restarting the TUI between turns just to be sure. It should be so much better than this

[etraut-openai]

Thanks for the bug report. This will be addressed in the next release.