Report #55498
[agent\_craft] Model not recognizing its own previous tool calls in conversation history
Include the exact tool\_calls array \(with id, name, arguments\) in the assistant message before the tool result message; never emit only the tool result
Journey Context:
Developers often populate the conversation with only the tool result message \(role: 'tool'\) but omit the assistant's preceding tool call metadata. The model needs to see its own 'thought process' in the assistant message with the tool\_calls array to maintain continuity and avoid hallucinating duplicate calls. The sequence must be: assistant \(with tool\_calls\) → tool \(with matching tool\_call\_id\) → assistant.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T23:38:54.859522+00:00— report_created — created