Cairn

Gemini systemInstruction missing role field causes HTTP 500

NousResearch/hermes-agent · cluster 20244 · agent

Data as of

Nothing open on GitHub. Fix merged in #45605. Check it covers your case.

The short answer

0open issues
0open PRs
7items grouped
Known?
Yes. 7 related items grouped here, 2 issues already closed.
Fix event
A fix was merged to main in PR #45605. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this partially resolved, deciding PR #45605. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug where the systemInstruction payload sent to Gemini/Gemma models omitted a required role field, resulting in HTTP 500 errors. Multiple fix attempts address this by adding the missing role field to the native adapter.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #45605 fix(gemini): add role field to systemInstruction

    merged to main

    files: agent/gemini_native_adapter.py, scripts/release.py, tests/agent/test_gemini_native_adapter.py

4 PRs closed without merging

From the close comments: merged via another change 3 · done elsewhere 1

  • #27123 fix(gemini): add missing role field to systemInstruction for Gemma compatibility · merged via another change → 018009b, #55585, #27123
  • #27159 fix(gemini): include role in native systemInstruction payload · merged via another change → a33bb14, #45605, #36047
  • #27215 fix(gemini): add required role field to systemInstruction in native adapter · done elsewhere → eed61a1, #45605, #27121
  • #36047 fix(gemini): add role field to systemInstruction for Gemma compatibility (#27121) · merged via another change → eed61a1, #45605
Closed issues · 2
  • Closed#20244[Bug]: Error: HTTP 500: Gemini HTTP 500 (INTERNAL): Internal error encountered.
  • Closed#27121fix(gemini): systemInstruction missing required role field causes HTTP 500 on Gemma models
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.26: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means 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

At a glance

Subsystem
agent
Merged PRs
#45605
Closed issues
2
Attempts
4 PRs closed without merging
Fix link checked
13 Jun 2026

For your agent

The same facts, typed.

cluster/20244.json
cluster/20244.md