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

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_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗