Terminal processes persist and become inaccessible after leaving unsaved threads
Open 💬 3 comments Opened Feb 5, 2026 by SarahVanDenBerghe
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
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?
- Click “New Thread” and do not send any chat messages.
- Open a terminal inside the new thread.
- Start a process (e.g.
npm run dev). - Navigate away from the new thread by switching to an existing thread/chat.
- Verify whether the terminal process continues running in the background.
- 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_
3 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Answer here: https://github.com/openai/codex/issues/10767
@jif-oai I'm a bit confused, I'm not using the CLI-tools, but the interface. Ideally, my terminal that was created within the interface, would just stay active as a new thread, or close properly if thread closes.
Currently the terminal process keeps on running, but with no way to access that terminal anymore from UI, it has disappeared.