Esc or Control+C does not kill running process have to kill the conversation at all
Resolved 💬 2 comments Opened Oct 29, 2025 by juslintek Closed Nov 28, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
0.50.0
What subscription do you have?
Team
Which model were you using?
gpt-5-codex
What platform is your computer?
Darwin 25.0.0 arm64 arm
What issue are you seeing?
clicking esc on running npm run e2e:test did nothing it was not able to stop or kill it pressing Ctrl+C once didn't stop it, so had to do it twice and kill the conversation without ability to follow up on it, context is gone.
What steps can reproduce the bug?
Uploaded thread: 019a30cd-e300-7770-8b5f-2c01eacdb6d2
What is the expected behavior?
When clicking esc or Ctrl+C it kills command that it is running without killing codex process itself, so you can followup and change direction of the conversation.
Additional information
_No response_
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I think this bug has been fixed in recent versions. If you see it again with the latest version of the CLI, let us know.