Terminal processes persist and become inaccessible after leaving unsaved threads

What version of the Codex App are you using (From “About Codex” dialog)?

260204.1342 (531)

What subscription do you have?

Plus

What issue are you seeing?

Terminal processes started inside a new thread continue running in the background after navigating away from the thread when it is not saved. The terminal session also becomes inaccessible from the interface, leaving no way to navigate back to or manage the running process.

What steps can reproduce the bug?

1. Click “New Thread” and do not send any chat messages.
2. Open a terminal inside the new thread.
3. Start a process (e.g. npm run dev).
4. Navigate away from the new thread by switching to an existing thread/chat.
5. Verify whether the terminal process continues running in the background.
6. Attempt to access or stop the running terminal process (created at step 3) from the interface.

What is the expected behavior?

One of the following should occur:

• The terminal process stops when leaving or closing the thread, or
• The thread is automatically saved/persisted so the terminal session remains valid and associated with that thread.

Additional information

_No response_