Invalid request parameters - Codex
Quick fix
OpenCode-Go's mimo-v2.6-flash fails when it does not natively support /responses; this issue provides no verified fix.
Symptom
Section titled “Symptom”CC Switch local proxy failed while handling Codex endpoint /responses. Provider: OpenCode-Go chat; model: mimo-v2.6-flash; upstream_status: HTTP 400; cause: data: {"error":{"param":"","type":"server_error","message":"Streaming response failed: [400] Invalid request parameters"}}Issue #7608 reports that on Windows with cc-switch 3.20.4, Codex received HTTP 400 from the `/responses` endpoint when requesting OpenCode-Go's mimo-v2.6-flash through the local proxy. The reporter believed the subscription, unlike DeepSeek, does not natively support the `responses` protocol, causing the streaming response to fail with `Invalid request parameters`.
The reporter expected cc-switch to route `reasoning_content` correctly, but the issue remains open. It provides no maintainer-confirmed or user-verified configuration change, version fix, or workaround.
Confirm that the failing request uses Codex's `/responses` endpoint, with Provider set to OpenCode-Go chat and model set to `mimo-v2.6-flash`.
This issue provides no verified fix steps. Until an update supports the `responses` protocol or correctly routes `reasoning_content`, this issue cannot confirm a successful configuration change.
Affected Versions
Section titled “Affected Versions”Source Issues
Section titled “Source Issues”This page is distilled from 1 real issues
(No FAQ yet)
Related problems
Section titled “Related problems”This is an unofficial community wiki with no affiliation to the cc-switch authors or the project itself. Its content is compiled from the project's public GitHub issues. This site distributes no software.