NousResearch/hermes-agent

Gemini AI Studio AQ. key routing behavior

Cluster 115306. Data as of

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

The short answer

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

A bug was reported where AI Studio AQ. keys stopped working, followed by fixes and documentation addressing how those keys are routed between the AI Studio and Vertex surfaces. The members center on the correct handling of AQ. key surface routing in the Gemini integration.

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.

  • #116820 fix(gemini): AI Studio AQ. keys stay on the Studio surface instead of being rerouted to Vertex and 403ing (#115306, salvage #115323)

    merged to main

    files: agent/gemini_native_adapter.py, contributors/emails/[redacted:email], hermes_cli/doctor_connectivity.py, hermes_cli/web_routers/config_env.py, tests/agent/test_gemini_key_surface_guidance.py, tests/agent/test_gemini_native_adapter.py, tests/hermes_cli/test_gemini_express_key_probes.py, tools/tts_streaming.py, tools/tts_tool_providers.py, website/docs/guides/google-gemini.md

2 PRs closed without merging

From the close comments: merged via another change 2

  • #115323 fix(gemini): stop rerouting AQ. keys off the default Studio surface · merged via another change → 232e4c3, #116820, #115306, #115323
  • #116202 docs(gemini): AQ. keys no longer identify the surface — document the configured-base contract · merged via another change → 232e4c3, #116820, #115306, #115323
Closed issues · 1
  • Closed#115306[Bug]: AQ. Gemini keys from Google AI studio no longer work
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.67: 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
#116820
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
20 Sep 2026

For your agent

The same facts, typed.