### What version of Codex is running? codex-cli 0.7.0 ### Which model were you using? o3-2025-04-16 ### What platform is your computer? Linux host, docker image ruby:3.3.1 with node 22.12.0 ### What steps can reproduce the bug? ```bash codex -c model=o3-2025-04-16 \ -c sandbox.permissions=disk-full-read-access \ -c sandbox.mode=workspace-write ``` ### What is the expected behavior? - The model responds to feedback and changes the next steps. - When an iteration is interrupted

After the current task execution is interrupted, it is not possible to start the next iteration

Resolved 💬 5 comments Opened Jul 15, 2025 by otrub Closed Oct 27, 2025

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

What version of Codex is running?

codex-cli 0.7.0

Which model were you using?

o3-2025-04-16

What platform is your computer?

Linux host, docker image ruby:3.3.1 with node 22.12.0

What steps can reproduce the bug?

codex -c model=o3-2025-04-16 \
	    -c sandbox.permissions=disk-full-read-access \
	    -c sandbox.mode=workspace-write

What is the expected behavior?

The model responds to feedback and changes the next steps.
When an iteration is interrupted, subsequent user input continues the normal iteration process.

What do you see instead?

When trying to give feedback on an iteration, it is not taken into account by the model and the approval iteration is repeated again.
Once an iteration is interrupted, further work is impossible.

ERROR: Turn interrupted

event                                                                                                                                       
BackgroundEvent(BackgroundEventEvent { message: "stream error: unexpected status 400 Bad Request: {\n  \"error\": {\n    \"message\": \"No  
tool output found for function call call_jYMLcaLzHr01TycvFpqSMCAq.\",\n    \"type\": \"invalid_request_error\",\n    \"param\": \"input\",\n
   \"code\": null\n  }\n}; retrying 10/10 in 2.122s…" })                                                                                    
                                                                                                                                            
ERROR: unexpected status 400 Bad Request: {  "error": {    "message": "No tool output found for function call
call_jYMLcaLzHr01TycvFpqSMCAq.",    "type": "invalid_request_error",    "param": "input",    "code": null  }}

Additional information

_No response_

View original on GitHub ↗

5 Comments

otrub · 1 year ago

It looks like the feedback mechanism doesn't work at all in my case.

crw2998 · 1 year ago

I have this issue as well. I have seen it in codex-rs for at least the last few versions.

Roundlay · 1 year ago

Same issue here. Occurs with at least GPT-4.1 and o3. It's a real deal breaker because it means that denying a patch or attempting to give feedback effectively ends the conversation!

nakamurau1 · 1 year ago

Hitting the same issue here on macOS.

Environment:

codex-cli 0.21.0 (npm)
macOS 14.6.1
Node v22.18.0
Repro in both VSCode integrated terminal and iTerm2

What happens:
Type something, hit enter, and I get:

🖐  Turn interrupted
▌[13;1R

After that, the CLI is totally frozen — Enter/Ctrl+C won’t recover it.

etraut-openai contributor · 10 months ago

I suspect this issue is no longer relevant. I'm going to presumptively close it. If anyone is still seeing this behavior, please let us know, and I'll reopen for investigation.