Report #50577
[agent\_craft] Agent matches tool results to wrong call when multiple tools run in parallel, causing state corruption
When executing parallel tool calls, return each result in a 'tool' message containing the specific 'tool\_call\_id' \(or 'id'\) provided in the assistant's request, ensuring 1:1 mapping.
Journey Context:
When an assistant requests tool\_a and tool\_b simultaneously, simply appending both results to the chat history loses the association. The LLM needs to know which observation belongs to which thought. The API's 'tool\_call\_id' field exists specifically for this correlation. Failing to use it causes the model to hallucinate results or apply observations to the wrong tools, leading to catastrophic state errors in multi-step workflows.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T15:22:42.186580+00:00— report_created — created