HTTP 400 unknown model 'ark-code-latest' - Codex
Quick fix
Change the MiniMax provider model ID in CC Switch from the Volcengine-only ark-code-latest to MiniMax-M3 to resolve this 400.
Symptom
Section titled “Symptom”CC Switch local proxy failed while handling Codex endpoint /responses. Provider: MiniMax; model: ark-code-latest; upstream_status: HTTP 400; cause: invalid params, code: 2013, msg: invalid params, unknown model 'ark-code-latest' (2013)This cluster holds three different MiniMax HTTP 400 variants. The main one: configuring the MiniMax provider with the Volcengine-only model ID `ark-code-latest` by mistake, which the MiniMax endpoint does not recognise, returning 400.
The other two: older versions such as v3.16.3 producing `invalid function arguments json string` from the Responses-to-Chat conversion during tool calls (fixed in v3.16.4 by switching to the native OpenAI Responses endpoint); and a `role` field validation error when handling images (still Open on v3.19.0+).
Open CC Switch settings and find the MiniMax provider config that errored.
Change the Model ID field from `ark-code-latest` to a model MiniMax officially supports, `MiniMax-M3` for example.
Save the config and send the request again. If it persists, delete that provider and recreate it from the MiniMax preset.
Upgrade CC Switch to v3.17.0 or newer. The new version adds a separate default model input to the Codex provider form, avoiding model ID confusion. For an `invalid function arguments json string` error, upgrade to v3.16.4 or newer.
Affected Versions
Section titled “Affected Versions”Source Issues
Section titled “Source Issues”This page is distilled from 3 real issues
- Why is `ark-code-latest` in my MiniMax config?
- Usually a copy-paste slip while following a tutorial or comparing configs. `ark-code-latest` is the model ID for the Volcengine (Agentplan/BytePlus) preset, not a MiniMax model.
- Does upgrading CC Switch prevent this configuration mistake?
- Yes. From v3.17.0, CC Switch adds a separate "default model" input to the Codex provider form and fixed the model suggestion dropdown retaining old models after a provider switch, making the mistake less likely.
- I get an `invalid function arguments json string` 400. Is that also a wrong model?
- No. That is a tool parameter JSON anomaly from converting the Responses endpoint to Chat in older versions. Upgrade CC Switch to v3.16.4 or newer — MiniMax now uses the native OpenAI Responses endpoint and this is fixed.
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.