Skip to content
CC Switch WikiUnofficial Community Wiki

unknown type: tool_search_call — Codex session continuation 400

Quick fix

Do not resume a thread containing tool_search_call history; start a new Codex thread before using the Responses upstream.

Symptom

Section titled “Symptom”
Error output
{"error":{"message":"CC Switch local proxy failed while handling Codex endpoint /responses. Provider: 88api; model: deepseek-v4-pro; upstream_status: HTTP 400; cause: The parameter `***.type` specified in the request are not valid: `The parameter `***.type` specified in the request are not valid: unknown type: tool_search_call.`. Request id: 021790042768713252c31405ea13a3faffc9ac5530b150ca5eece","type":"BadRequest","code":"InvalidParameter","param":"input.type","provider":"88api","model":"deepseek-v4-pro","endpoint":"/responses","upstream_status":400}}

Cause

Section titled “Cause”

Codex writes tool_search_call and tool_search_output to the conversation history. After switching to a native /v1/responses upstream, the CC Switch local proxy forwards input[] unchanged. A strict third-party upstream does not recognize tool_search_call, so it rejects the request with HTTP 400 before the model is called. Historical items are replayed in later turns, so the same thread keeps failing; switching models does not help.

This differs from converting the tools[] declaration or bridging Responses to chat/completions. When closing this issue, the maintainer said the cause lies on the client or provider side and cannot be fixed in CC Switch itself.

Fix

Section titled “Fix”

  1. Do not resume a thread containing tool_search_call / tool_search_output history; continue in a new Codex thread. The maintainer noted that this issue cannot be fixed in CC Switch itself.

  2. Advanced users can back up the rollout JSONL first, then edit the history file to remove the relevant items; the issue cautions that ordinary users should not have to do this.

Affected Versions

Section titled “Affected Versions”
ToolCodex
VersionCodex desktop app 26.915.31945；codex-cli 0.155.0-alpha.9.2
PlatformsmacOS

Source Issues

Section titled “Source Issues”

This page is distilled from 1 real issues

FAQ

Section titled “FAQ”

(No FAQ yet)

Section titled “Related problems”
cc-switch Usage Statistics Differ from DeepSeek Official Site / Stop UpdatingUpgrade to v3.19.2 or later, then run “Rebuild Codex Usage” once on the “Usage Statistics” page to correct historical overcounts or missing records.22 issues mergedCodex config.toml completely overwrittenMost related issues remain unresolved. Put custom sections in cc-switch’s common configuration or provider template, then upgrade to the latest version. (MCP)15 issues mergedNo tool output found for tool callNo official fix is confirmed. The reporter describes a local workaround that reorders tool calls and outputs. Follow the main issue for progress.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.