You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
OpenAI Chat tool call delta is missing id or name #52700
Additional evidence from a different provider/model — plus a related silent-failure variant.
Environment: OpenCode V2, provider opencode-go, models mimo-v2.5 and mimo-v2.6-flash.
Hard-fail path (this issue's error): 2026-10-04 22:05:53–22:05:58 UTC, three background subagent result calls all returned:
[ERROR] OpenAI Chat tool call delta is missing id or name
Tasks task_b2fe62bb, task_1eb2bb0f, task_57fa8495 died ~160s into their runs; repeated failures then tripped Circuit breaker OPEN for general. Try again later. (first hit 22:08:44 UTC, still firing at 23:29:36) — delegation was blocked for ~84 minutes. Nine delegated tasks errored in total that session.
Silent-drop variant (no error raised): the same session's compress tool calls were recorded by the client with empty arguments:
The assistant's reasoning in the same message shows the full content array being composed, and the rendered transcript shows compress({}) — the args were streamed but never landed in the recorded input, no missing id or name error was raised, the tool executed with {}, and the downstream proxy rejected it (no valid ranges parsed (kind=missing-content, dropped=0)). 8 such failures on 2026-09-25; identical argument format succeeded later in the same session, so this is not an argument-encoding problem.
Cross-session scale (local session store scan, 6.0 GB): 7 sessions contain no valid ranges parsed markers — worst has 116, this session 25 (and 25 delta-error rows / 19 circuit-breaker rows).
Suggestion: the malformed-delta handling appears to have two outcomes depending on where the delta breaks — a hard error (missing id/name) or silently accepting a tool call with zeroed arguments. The second one is the more dangerous: the tool runs on empty input and the failure surfaces much later in an unrelated component.
Activity
github-actions commentedon Oct 2, 2026
This issue doesn’t fully meet our contributing guidelines.
What needs to be fixed:
Please edit this issue to address the above within 72 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
fledge-alpha-freeand describes a finaltool_callschunk with no tool-call delta.id/namedeltas.If you believe this was flagged incorrectly, please let a maintainer know.
Taliyaha commentedon Oct 2, 2026
I don't know why it suddenly got better, please delete this feedback!
Selene0623 commentedon Oct 4, 2026
Additional evidence from a different provider/model — plus a related silent-failure variant.
Environment: OpenCode V2, provider
opencode-go, modelsmimo-v2.5andmimo-v2.6-flash.Hard-fail path (this issue's error): 2026-10-04 22:05:53–22:05:58 UTC, three background subagent result calls all returned:
Tasks
task_b2fe62bb,task_1eb2bb0f,task_57fa8495died ~160s into their runs; repeated failures then trippedCircuit breaker OPEN for general. Try again later.(first hit 22:08:44 UTC, still firing at 23:29:36) — delegation was blocked for ~84 minutes. Nine delegated tasks errored in total that session.Silent-drop variant (no error raised): the same session's
compresstool calls were recorded by the client with empty arguments:{"type":"tool","id":"call_4f80f0b9df644ad993bd69f7","name":"compress","executed":false,"state":{"status":"completed","input":{}, ...}}The assistant's reasoning in the same message shows the full content array being composed, and the rendered transcript shows
compress({})— the args were streamed but never landed in the recorded input, nomissing id or nameerror was raised, the tool executed with{}, and the downstream proxy rejected it (no valid ranges parsed (kind=missing-content, dropped=0)). 8 such failures on 2026-09-25; identical argument format succeeded later in the same session, so this is not an argument-encoding problem.Cross-session scale (local session store scan, 6.0 GB): 7 sessions contain
no valid ranges parsedmarkers — worst has 116, this session 25 (and 25 delta-error rows / 19 circuit-breaker rows).Suggestion: the malformed-delta handling appears to have two outcomes depending on where the delta breaks — a hard error (missing id/name) or silently accepting a tool call with zeroed arguments. The second one is the more dangerous: the tool runs on empty input and the failure surfaces much later in an unrelated component.
Cross-reference: ranxianglei/billion-context#1366 (proxy-side view of the empty-args symptom).
github-actions commentedon Oct 5, 2026
This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 72-hour window.
Feel free to open a new issue that follows our issue templates.