codex - 💡(How to fix) Fix Using codex-cli 0.121.0 with openrouter fails [1 comments, 2 participants]

■ {"error":{"code":"invalid_prompt","message":"Invalid Responses API request"},"metadata":{"raw":"[\n {\n "code": "invalid_union",\n "errors":[\n [\n {\n "code": "invalid_union",\n "errors": [],\n "note": "No matching discriminator",\n"discriminator": "type",\n "path": [\n "type"\n ],\n "message": "Invalid input"\n }\n ],\n[\n {\n "code": "invalid_value",\n "values": [\n "openrouter:datetime"\n ],\n "path": [\n"type"\n ],\n "message": "Invalid input: expected \"openrouter:datetime\""\n }\n ],\n [\n {\n"code": "invalid_value",\n "values": [\n "openrouter:image_generation"\n ],\n "path": [\n"type"\n ],\n "message": "Invalid input: expected \"openrouter:image_generation\""\n }\n ],\n [\n {\n"code": "invalid_value",\n "values": [\n "openrouter:experimental__search_models"\n ],\n "path": [\n"type"\n ],\n "message": "Invalid input: expected \"openrouter:experimental__search_models\""\n }\n ],\n [\n{\n "code": "invalid_value",\n "values": [\n "openrouter:web_search"\n ],\n "path": [\n"type"\n ],\n "message": "Invalid input: expected \"openrouter:web_search\""\n }\n ]\n ],\n "path": [\n"tools",\n 15\n ],\n "message": "Invalid input"\n }\n]"}}

TL;DR

Downgrade to Codex CLI version 0.120.0 as a temporary workaround to resolve the "invalid_prompt" error.

Guidance

• The error message indicates an "invalid_union" issue with the "type" discriminator, suggesting a compatibility problem between the Codex CLI version and the API expectations.
• Verify that the ~/.codex/config.toml file is correctly set up according to the official documentation, as any misconfiguration could exacerbate the issue.
• Consider waiting for an update to the Codex CLI that addresses this compatibility issue, as downgrading might not be a long-term solution.
• If the issue persists after downgrading, re-check the API key and configuration for any potential mismatches or updates required for version 0.120.0.

Notes

The provided error message and the fact that downgrading to version 0.120.0 resolves the issue suggest a version-specific problem. Without further details on the changes between versions 0.120.0 and 0.121.0, it's challenging to provide a more targeted fix.

Recommendation

Apply the workaround by downgrading to version 0.120.0, as it has been confirmed to work as expected, allowing for temporary resolution of the issue until a more permanent fix is available.