BUG: Status 400 Missing required parameter input[133].id
Resolved 💬 12 comments Opened Nov 19, 2025 by trethore Closed Dec 8, 2025
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
0.59
What subscription do you have?
Plus
Which model were you using?
gpt5.1-codex-max (medium)
What platform is your computer?
windows wsl
What issue are you seeing?
This bug happened midway through the chat with the model.
unexpected status 400 Bad Request: {
"error": {
"message": "Missing required parameter: 'input[133].id'.",
"type": "invalid_request_error",
"param": "input[133].id",
"code": "missing_required_parameter"
}
}What steps can reproduce the bug?
Uploaded thread: 019a9d7b-5f0d-7b52-aa07-024594d6e04e
I don’t know much about it, so I hope this thread helps.
What is the expected behavior?
Answer correctly to my requests.
Additional information
_No response_
Current fix
Set web_search_request = false in your config.toml.
It seems that tool calls are currently broken with this model.
12 Comments
I've had the same thing:
■ unexpected status 400 Bad Request: {
"error": {
"message": "Missing required parameter: 'input[17].id'.",
"type": "invalid_request_error",
"param": "input[17].id",
"code": "missing_required_parameter"
}
}
This is still happening in v0.60.1, at least when using a thread created in v0.59.
Same issue - can't do anything with the model right now
■ unexpected status 400 Bad Request: {
"error": {
"message": "Missing required parameter: 'input[1145].id'.",
"type": "invalid_request_error",
"param": "input[1145].id",
"code": "missing_required_parameter"
}
}
Same cant /compact as well
I'm seeing this exact behavior as well.
Guys, turn off web_search_request
broken
Same error with different input IDs: 019a9dca-5b25-7643-a5cd-ee943aa36ea2 (5.1-codex-max-high) and 019a9de5-1f98-7fb0-a21e-a8acad8310b4 (GPT-5.1.)
Can confirm this works as a workaround for now
Probably it is landing in https://github.com/openai/codex/pull/6943
Any update on this? I found something similar to https://github.com/openai/codex/issues/6968
I think this has been fixed. Let us know if you're still seeing it with the latest version.