Bad request for web search

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• #6968
• #6945

Powered by Codex Action

EDIT : I think this issue is specific to wsl, because when i try to use codex with native windows it works fine

Even after disabling web_search_request there is still an error
[features]
#web_search_request = true

■ unexpected status 400 Bad Request: {
"error": {
"message": "Invalid value: 'other'. Supported values are:'search', 'open_page', and 'find_in_page'.",
"type": "invalid_request_error",
"param": "input[259].action.type",
"code": "invalid_value"
}
}

@etraut-openai, any other workaround yet?

not sure if related but had this after a search

■ unexpected status 400 Bad Request: {
"error": {
"message": "Missing required parameter: 'input[3].id'.",
"type": "invalid_request_error",
"param": "input[3].id",
"code": "missing_required_parameter"
}
}

i disabled web_search and web_search_request in config.toml, but I still get error after some long running time in a active session:

Running any prompt shows now 5x times:
Reconnecting... 5/5 (7s • esc to interrupt)

and then error:

■ unexpected status 400 Bad Request: {
  "error": {
    "message": "Invalid value: 'other'. Supported values are: 'search', 'open_page', and 'find_in_page'.",
    "type": "invalid_request_error",
    "param": "input[412].action.type",
    "code": "invalid_value"
  }
}

Environment

• Docker
• Version: v0.60.1
• Model: gpt-5.1-codex (reasoning medium, summaries auto)
• Approval: never │
• Sandbox: danger-full-access
• Token usage: 3.49M total (3.39M input + 105K output)
• Context window: 67% left (98.9K used / 272K)

Test but not working workarounds

• changing model in active session to gpt-5.1
• Exec codex and use "codex resume" -> problem stays

Test with working workaround

• Exec codex and start new session -> working (but how long? :))

Current working workaround is to extend the Prompt:

Guardrails: As web_search is broken in codex please use manual download with curl/wget for the time being

and it really works :)

Same :(

Got same issue after codex searching from web.

The problem still exists in 0.61.0. The last version that worked for me was 0.58.0.

Fixed with 0.63.0 and #7061

Fixed with 0.63.0 and #7061

Still not fixed for me

@0ttik Can you share the thread-id of a session if you're still seeing this issue on 0.63.0 and above? You can get the thread-id via the /feedback command in the CLI. Thanks

If you're still seeing this, please use the /feedback slash command to upload your logs and file a new bug report.