codex - 💡(How to fix) Fix Process termination messages are printed over the Codex CLI input box [1 comments, 2 participants]

What version of Codex CLI is running?

0.130.0

What subscription do you have?

ChatGPT Plus

Which model were you using?

gpt-5.5

What platform is your computer?

Windows 11 x64

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

Windows Terminal with PowerShell7

What issue are you seeing?

After Codex finished a task, several Windows process termination messages were printed at the bottom of the TUI and overlapped with the input area.

The messages looked like:

SUCCESS: The process with PID 21444 (child process of PID 20280) has been terminated.
SUCCESS: The process with PID 14000 (child process of PID 20280) has been terminated.
SUCCESS: The process with PID 5768 (child process of PID 21552) has been terminated.
SUCCESS: The process with PID 20280 (child process of PID 21348) has been terminated.
SUCCESS: The process with PID 21552 (child process of PID 21348) has been terminated.

These messages appeared inside/over the area where I was typing the next prompt. The input still worked, but the TUI layout looked corrupted and the process cleanup output mixed with my prompt text.

What steps can reproduce the bug?

1. Run Codex CLI on Windows in a PowerShell terminal.
2. Ask Codex to perform a task that starts child/background processes.
3. Let the task finish.
4. Codex performs cleanup and terminates child processes.
5. Observe the bottom input area of the Codex TUI.

In my case, this happened after Codex completed a git commit/push/package task:

• committed changes
• pushed to origin/main
• ran npm run pack:unpacked
• reported the working tree was clean
• then several SUCCESS: The process with PID ... has been terminated. messages appeared over the input area

What is the expected behavior?

Process cleanup/termination messages should not be printed into the interactive input area.

They should either be:

• captured and displayed as normal command output in the conversation log,
• hidden/suppressed if they are internal cleanup messages,
• or followed by a clean TUI re-render.

The input box should remain visually clean and should not be overwritten by background process termination output.

Additional information

This seems specific to Windows process cleanup output. The task itself completed successfully, but after cleanup the TUI did not redraw correctly and the termination messages polluted the prompt/input area.