invalid function arguments json string: Codex
Quick fix
Upgrade cc-switch to 3.16.4 or later, then retest with MiniMax-M3.
Symptom
Section titled “Symptom”CC Switch local proxy failed while handling Codex endpoint /responses. Provider: MiniMax; model: MiniMax-M3; upstream_status: HTTP 400; cause: invalid params, invalid function arguments json string, tool_call_id: call_function_ou9fwsqecq27_1 (2013)This report occurred when Codex called MiniMax-M3 through the cc-switch local proxy: the JSON string for tool-call arguments was invalid, causing the upstream to return HTTP 400 (2013) and preventing the session from continuing.
The maintainer stated that v3.16.4 restored the historical function_call field for Codex tool calls, prevented empty streaming deltas from overwriting tool-call state, and changed MiniMax domestic and international versions to use the native OpenAI Responses API instead of Responses→Chat conversion. These changes may cover the issue, but the original post did not confirm the retest result, so this is not a verified fix.
Upgrade cc-switch from 3.16.3 to 3.16.4 or later.
Retest tool calls with MiniMax-M3 in Codex. If the issue persists, reopen the original issue as the maintainer advised and include the latest version and logs.
Affected Versions
Section titled “Affected Versions”Source Issues
Section titled “Source Issues”This page is distilled from 1 real issues
- What if the issue still occurs after upgrading?
- The maintainer recommends reopening the issue and including the latest version and logs for further investigation.
- Has this fix been confirmed?
- Not yet. The maintainer only said the v3.16.4 changes may cover the issue and requested a retest after upgrading.
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.