Skip to content

failed to parse function arguments: EOF while parsing an object — Codex

Quick fix

No verified fix is available. Check Codex session logs for truncated arguments JSON, then report it to the upstream provider or switch providers.

Error output
failed to parse function arguments: EOF while parsing an object at line 1 column 1135

In Issue #5001, MiniMax-M3 stopped while streaming `response.function_call_arguments.delta`, without outputting the closing `}` or `response.function_call_arguments.done`. As a result, Codex failed when parsing incomplete `arguments` JSON locally. The report considers this unrelated to CC Switch's 2 KB buffer or proxy serialization-layer truncation.

A follow-up in the same discussion reported another `/responses` tool-call variant: the upstream returned `messages.2.tool_call_id 长度不足`. That report used a different upstream and model, and its root cause has not been confirmed. Both variants appear as an HTTP 400 error from CC Switch, but the original post says the error does not clearly distinguish upstream validation failure from incomplete tool arguments received by the client. The issue remains open and provides no verified fix.

  1. The original post provides no verified solution. Check Codex session logs for `failed to parse function arguments`, and confirm whether the tool-argument JSON is missing closing characters.

  2. Report the truncated tool-call record to the upstream provider, or switch to another provider. This is the root-cause direction proposed by the original post and was not confirmed as successful in this issue.

ToolCodex
Version3.16.5 - 3.20.1(报告版本,非已确认影响范围)
PlatformsWindows

(No FAQ yet)

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.