Unexpected 400 Bad Request error when using gpt-5.1-codex-max with unsupported tool type #7065
Description
What version of Codex is running?
0.61.0
What subscription do you have?
Pro
Which model were you using?
gpt-5.1-codex-max
What platform is your computer?
macOS using iTerm2
What issue are you seeing?
When using the GPT‑5.1 Codex Max model, I encountered an error when a tool call was made. The request returned an unexpected 400 Bad Request status with the following JSON payload:
{
"error": {
"message": "Invalid value: 'other'. Supported values are: 'search', 'open_page', and 'find_in_page'.",
"type": "invalid_request_error",
"param": "input[129].action.type",
"code": "invalid_value"
}
}
It looks like the model attempted to call a tool action type labeled other, which is not supported. Only search, open_page, and find_in_page are valid actions. This causes the conversation to break with a 400 error instead of executing the intended tool call.
What steps can reproduce the bug?
- Launch Codex CLI (version 0.59.0 or similar) and choose the gpt‑5.1-codex-max model.
- Initiate a conversation that causes the model to call a tool action. In my case, the model called a tool with type
other(perhaps triggered by certain commands or connectors). - Observe the response: the CLI returns a
400 Bad Requeststatus with an error indicating thatotheris an invalid action type.
What is the expected behavior?
The model should only call supported tool action types (e.g., search, open_page, or find_in_page) when using GPT‑5.1 Codex Max. If an unsupported action is attempted, it should be gracefully handled or mapped to the correct tool rather than returning a 400 error. Ideally, the conversation should continue without breaking and the appropriate tool should be invoked.
Additional information
No response