Skip to content
CC Switch WikiUnofficial Community Wiki

tools.function.parameters.type is required and must be "object" — Codex

Quick fix

Upgrade cc-switch to v3.18.0 to fix Codex tool parameter schemas rejected by strict upstreams with HTTP 400.

Symptom

Section titled “Symptom”
Error output
CC Switch local proxy failed while handling Codex endpoint /responses. Provider: Kimi For Coding; model: kimi-for-coding; upstream_status: HTTP 400; cause: tools.function.parameters.type is required and must be "object"

Cause

Section titled “Cause”

Codex's built-in tool `codex_app__automation_update` may carry a schema whose `parameters` is `null`, lacks `type`, or uses a top-level `oneOf` union without an explicit `type: "object"`. When cc-switch converts Codex Responses requests into Chat Completions requests for upstreams such as DeepSeek and Kimi, upstreams that strictly validate schemas return HTTP 400.

The maintainer states this was fixed in v3.18.0: the proxy conversion layer normalizes tool `parameters` into an object schema, covering the `null`, missing, and top-level union cases.

Fix

Section titled “Fix”

  1. Upgrade cc-switch to v3.18.0, then use Codex to call the provider.

  2. If it still reproduces after upgrading, attach debug logs as requested by the maintainer and reopen the corresponding issue.

Affected Versions

Section titled “Affected Versions”
ToolCodex
Versionv3.18.0（已修复）
PlatformsWindowsmacOS

Source Issues

Section titled “Source Issues”

This page is distilled from 4 real issues

FAQ

Section titled “FAQ”
Is it true that the cc-switch API cannot let Codex call tools and can only chat?
No. This HTTP 400 is a tool parameter schema conversion compatibility issue; the maintainer states it was fixed in v3.18.0.
Both Kimi K2.7 and DeepSeek report 400; how do I fix it?
These reports are the same class of tool parameter schema validation failure; upgrade to v3.18.0 and verify.
Section titled “Related problems”
invalid thinkingKimi's deepseek-v4-flash rejects the current thinking parameter; the original post provides no verified solution.1 issues mergedUpstream HTTP 404 - DeepSeekResolve based on the scenario: if the endpoint path is the issue, complete the API address with the full API root (such as `.../v1`); if the model… (cc-switch)6 issues mergedCC Switch is currently a black box; users cannot customize processing logicThis is a feature request for programmable routing transformation scripts in CC Switch; the original post has no verifiable official solution.1 issues merged

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.