Automatic approval review failed: Codex automatic approval with MiMo failed
Quick fix
Use a model that supports json_schema for Codex automatic approval, or wait for CC Switch to provide a compatible fallback for MiMo.
Symptom
Section titled “Symptom”Rejected("This action was rejected due to unacceptable risk.
Reason: Automatic approval review failed: {
"error":{
"message":"CC Switch local proxy failed while handling Codex endpoint /responses. Provider: MiMo; model: mimo-v2.5; upstream_status: HTTP 400; cause: data:{
\"error\":{
\"code\":\"responses_feature_not_supported\",
\"message\":\"text.format type 'json_schema' is not supported, only 'text' and 'json_object' are allowed.\",
\"param\":\"\",
\"type\":\"unsupported_feature\"
}
}",
"type":"upstream_error",
"code":"cc_switch_upstream_error"
}
}")When Codex runs a command with `sandbox_permissions: "require_escalated"`, CC Switch forwards the automatic approval request to MiMo. The approval request uses the `json_schema` response format, but `mimo-v2.5` accepts only `text` and `json_object`, so the upstream returns HTTP 400.
Automatic approval fails before command execution, so all commands requiring elevated sandbox permissions are rejected. This issue is still open; the input contains no confirmed fixed version or fallback configuration.
Use a model that supports the `json_schema` response format for the Codex automatic approval flow.
If MiMo is required, wait for CC Switch to implement model capability detection or a simplified approval fallback when structured output is unsupported.
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.