bug: unable to continue after hitting esc esc to interrupt assistant

Resolved 💬 11 comments Opened Apr 16, 2025 by jamesheinlein Closed Aug 7, 2025

💡 Likely answer: A maintainer (jonchurch, contributor) responded on this thread — see the highlighted reply below.

after interrupting, it's not possible to continue usage without clearing the history. Subsequent messages consistently yield errors like:

⚠️  OpenAI rejected the request (request ID:
    req_***). Please verify your
    settings and try again.

View original on GitHub ↗

11 Comments

samreid · 1 year ago

I have seen the same problem Message: 400 No tool output found for function call after esc*esc then a message, in my usage.

jonchurch contributor · 1 year ago

I've seen a "tool returned empty" error message after ESC-ESC tapping, preventing me from sending any additional prompts.

Edit: reprod it again, error is:

system
    ⚠️  OpenAI rejected the request (request ID: req_00d561908c8f241e2162f1147ec3567b). Error details: Status: 400, Code:
    unknown, Type: invalid_request_error, Message: 400 No tool output found for function call call_JeQWN1nC6RRIEOf6RDl4AUMT..
    Please verify your settings and try again.

jamesheinlein · 1 year ago

this issue is not resolved.

jonchurch contributor · 1 year ago

@tibo-openai I can repro this pretty reliably, and am 80% of the way towards a fix. the 400 No tool output found issue Im referring to

If you want to reopen it and assign me the issue, I'll keep working on it.

I have a fix, but want to keep testing to ensure I understand what the agent loop is supposed to be doing, vs what Im actually observing at runtime.

The async nature of it all mixed w/ streams is a bit hard to hold in the head, and is due for some tightening up which can come after a fix.

tibo-openai collaborator · 1 year ago

Re-opening, @jonchurch ooc what is the fix you're referring to and would you be willing to contribute it as a PR? Looks like folks are still hitting this indeed.

golergka · 1 year ago

Hitting the same issue all the time, so far the most painful issue with codex that makes me restart it constantly, on version v0.1.04161210

    system
    ⚠️  OpenAI rejected the request (request ID: req_69b88ab21c1f8d38adfa0817e7771552). Error details: Status: 400, Code: unknown, Type: invalid_request_error, Message: 400 No tool output found for function call
    call_tIuWiXlxLsDXBZK2uZ972ILY.. Please verify your settings and try again.

tibo-openai collaborator · 1 year ago

@jonchurch Assigned this to you, but please let me know if you won't get to it and I will have a look later today.

jonchurch contributor · 1 year ago

Back at keyboard after the weekend, you'll see something before EoD from me on this

Want to clean up my work a bit.

WASasquatch · 1 year ago

Looking forward to this. I wasn't having this issue before, but suddenly getting it a over and over again. It looks to be having trouble specifically with a css file. It's just frustrating that instead of retrying, being aware of the error, and trying a different way like other systems, it just throws and error and exits.

Version 0.1.2504221401

darman96 · 1 year ago

I am getting this error event tough I didn't use Esc Esc before, I even cleared the command history to be sure.

codex-maintainers · 11 months ago

Thanks for the feedback! Please try again on the latest version of Codex CLI. If the issue persists, let us know. We're primarily focused on the native/Rust implementation of Codex CLI.