Fixes for dropped tool results due to ID mismatches
Cluster 63000 · agent. Data as of
Nothing open on GitHub. Fix merged in #93329. Check it covers your case.
The short answer
- Known?
- Yes. 5 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #93329. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #93329. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and fixes address a bug where tool results are silently dropped when tool call IDs have composite or variant formats (e.g., 'call_xxx|fc_yyy'), causing the model to never receive tool output. The work focuses on normalizing and correctly pairing tool call IDs across multiple matching sites in the agent pipeline.
Open issues0
Open PRs0
Fixes on record
-
#93329 fix(agent): tool results survive divergent id/call_id variants at all four pairing sites (#93251, salvages #56148 #58287 #66974 #91768)
files:
agent/agent_runtime_helpers.py,agent/context_compressor.py,tests/agent/test_context_compressor.py,tests/run_agent/test_message_sequence_repair.py,tests/run_agent/test_run_agent.py -
#93401 fix(agent): composite and response_item_id spellings pair correctly; results born on canonical ids (#63000, salvage #93335)
files:
agent/agent_runtime_helpers.py,agent/context_compressor.py,agent/conversation_loop.py,agent/message_sanitization.py,agent/tool_dispatch_helpers.py,agent/tool_executor.py,tests/agent/test_tool_dispatch_helpers.py,tests/run_agent/test_message_sequence_repair.py
2 PRs closed without merging
From the close comments: merged via another change 1 · other 1
Closed issues · 1
- Closed#63000Tool results silently dropped when provider returns composite tool_call ids (call_xxx|fc_yyy) — model never sees output and confabulates
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the Lab