Skip to content
CC Switch WikiUnofficial Community Wiki

No tool output found for tool call: missing Codex tool output

Quick fix

No official fix is confirmed. The reporter describes a local workaround that reorders tool calls and outputs. Follow the main issue for progress.

Symptom

Section titled “Symptom”
Error output
No tool output found for tool call call\_05\_VJLUQzBwxx8R9QvVr90i1460

Cause

Section titled “Cause”

The maintainer confirmed that `image_resize_notice` inserted after `view_image` separates `function_call` from `function_call_output`, which DeepSeek's `/responses` strictly rejects. The reporter could still reproduce this with Codex on cc-switch 3.20.2 and Windows. The issue was closed as a duplicate and consolidated into the main issue for tracking; closure does not mean it was fixed.

The reporter's local compatibility-layer proposal also handles interleaved developer/reasoning messages, genuinely missing tool outputs, orphaned or duplicate outputs, and malformed call arguments. These are scenarios the proposal claims to cover, not root causes individually confirmed by the maintainer. The post records self-tests, simulated upstream tests, and a 200 response from `/v1/models`, but does not verify that affected existing tasks ran successfully after a restart. Built-in support for this compatibility handling remains a feature request, with no evidence of implementation.

Fix

Section titled “Fix”

  1. Follow the link in the source issue to track fixes in the main issue. The maintainer recorded that the problem remained reproducible in 3.20.2; the post identifies no official version confirmed to resolve it.

  2. To evaluate a temporary workaround, refer to the reporter's custom Responses API compatibility layer: reorder tool calls and their corresponding outputs before forwarding, moving interleaved messages after the complete tool outputs. This is a user's local workaround. The post does not provide a complete implementation ready for reuse, and its local installation script must not be treated as an official component.

  3. If you have deployed the compatibility layer described in the post, follow its recommendation to restart Codex and reopen the affected existing tasks to verify that actual tool calls work again. A 200 response from `/v1/models` alone does not confirm that existing tasks have recovered. If your scenario differs materially, the maintainer recommends adding details and reopening the issue.

Affected Versions

Section titled “Affected Versions”
ToolCodex
Version3.20.2（cc-switch 受影响版本）
PlatformsWindows

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”
Codex desktop cannot see modelsSign in to official ChatGPT, enable “Keep official login when switching to third parties,” and enable local routing. Restart Codex.6 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 mergedThe `content[].thinking` in thinking modeSome variants remain unresolved: upgrade to a version with the thinking history normalization fix; for Codex routed through DeepSeek, use a version with the…13 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.