codex - 💡(How to fix) Fix Messages to be submitted after next tool call (press esc to interrupt and send immediately) not working on CLI [4 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#17095Fetched 2026-04-09 08:02:31
View on GitHub
Comments
4
Participants
3
Timeline
12
Reactions
0
Author
Timeline (top)
commented ×4labeled ×4cross-referenced ×1mentioned ×1
RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

codex-cli 0.118.0

What subscription do you have?

Enterprise

Which model were you using?

gpt-5.4

What platform is your computer?

Darwin 25.4.0 arm64 arm

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

No response

What issue are you seeing?

Messages to be submitted after next tool call (press esc to interrupt and send immediately) not working on CLI

What steps can reproduce the bug?

Steps to reproduce

  1. Open the CLI.
  2. Submit a prompt that triggers a long-running tool call.
  3. While the tool call is still running, type a follow-up message into the input box.
  4. Wait for the UI hint: Messages to be submitted after next tool call (press esc to interrupt and send immediately).
  5. Press Esc.

Nothing happens. The queued message is not sent immediately, and the CLI stays in the current tool-call state.

What is the expected behavior?

The queued message should be submitted immediately after pressing Esc, interrupting the current tool call.

Additional information

No response

extent analysis

TL;DR

The issue with messages not being submitted immediately after pressing Esc in the Codex CLI may be related to the current implementation of the tool call interruption mechanism.

Guidance

  • Verify that the Esc key is properly registered as the interrupt key in the Codex CLI configuration.
  • Check if there are any known issues or limitations with the gpt-5.4 model that might be causing the problem.
  • Try submitting a simple prompt to test if the issue is specific to long-running tool calls.
  • Investigate if there are any updates or patches available for the Codex CLI version 0.118.0 that might address this issue.

Example

No code snippet is provided as the issue does not contain sufficient information to create a relevant example.

Notes

The provided information does not include any details about the terminal emulator or version, which might be relevant to the issue. Additionally, there is no mention of any error messages or logs that could help diagnose the problem.

Recommendation

Apply workaround: The user could try using a different method to interrupt the tool call, such as using a different key or command, to see if the issue is specific to the Esc key.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING