Gemini consecutive same-role content merging fix
Cluster 55125. Data as of
Nothing open on GitHub. Fix merged in #55623 on 30 Jun 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #55623. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #55623. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a problem where parallel tool calls in native Gemini produce consecutive same-role content entries, causing a 400 error on Gemini's alternation check. The fix merges or coalesces such entries into a single turn.
Open issues0
Open PRs0
Fixes on record
-
#55623 fix(agent): merge consecutive same-role contents for native Gemini (#55125)
files:
agent/gemini_native_adapter.py,tests/agent/test_gemini_native_adapter.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1
Closed issues · 1
- Closed#55125Native Gemini: parallel tool calls emit consecutive same-role contents and 400 on the alternation check
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.50: 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 LabAt a glance
- Merged PRs
- #55623
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 30 Jun 2026