NousResearch/hermes-agent

Gemini fallback alias routing through native client

Cluster 104583. Data as of 2026-10-24 04:06 UTC

Nothing open on GitHub. Fix merged in #104911 on 7 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

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

Next step: read #104911, then check it covers your case.

Read #104911 Pick up a Lab task

These issues and PRs concern Google/Gemini fallback provider aliases bypassing GeminiNativeClient and sending unsupported parameters like 'thinking_config', resulting in 400 errors. The work focuses on routing those aliases correctly through the native client gate.

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.

#104911 fix: Gemini fallback aliases send native thinking requests (#104583, salvage #104584)

merged to main

files: agent/agent_runtime_helpers.py, contributors/emails/[redacted:email], tests/agent/test_gemini_alias_native_route.py, website/docs/user-guide/features/fallback-providers.md

2 PRs closed without merging

From the close comments: merged via another change 2

#104584 fix(gemini): route google-alias fallback providers through GeminiNativeClient · merged via another change → a745101, 1eb1b79, #104911, #104583, #104875
#104875 fix(agent): route gemini profile aliases through the native client gate (#104583) · merged via another change → #104583, #104911, #104584

Closed issues · 1

Closed#104583fallback_providers: "google" entry bypasses GeminiNativeClient, 400s with "Unknown name 'thinking_config'"

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.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

Merged PRs: #104911
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 7 Sep 2026

For your agent

The same facts, typed.

cluster/104583.json
cluster/104583.md