Evidence · DiggingBeagle record
Gemini CLI issue 30014: tool calls may repeat after a streaming retry
GitHub issue #30014 was opened October 29, 2026. The reporter traces function calls emitted from a failed streaming turn, their persistence through a Retry event, duplicate execution, and orphaned tool responses. The issue is not proof of an independently confirmed production-loss rate or a fixed version.
- Published
- Oct 29, 2026
- Source role
- primary disclosure
Evidence record
GitHub issue #30014 was opened October 29, 2026. The reporter traces function calls emitted from a failed streaming turn, their persistence through a Retry event, duplicate execution, and orphaned tool responses. The issue is not proof of an independently confirmed production-loss rate or a fixed version.
Claim-level citations (3)
- supportsGemini CLI streaming retry may execute the same tool effect twice: The issue report describes tool calls from both a failed streaming attempt and a later retry being executed.
Issue 30014, reported reproduction
- supportsGemini CLI streaming retry may execute the same tool effect twice: The reporter describes conversation/transcript inconsistency following the failed stream and retry.
Issue 30014, error and transcript output
- supportsGemini CLI streaming retry may execute the same tool effect twice: The issue reporter attributes duplicate tool effects to front ends retaining a streamed ToolCallRequest despite a subsequent Retry event, while chat history retains only the successful generation turn.
GitHub issue #30014, What happened? and proposed cause