Cairn

Gemini native fallback ignores user default_headers

NousResearch/hermes-agent · cluster 102788 · agent

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

These items address a bug where the Gemini-native fallback path in provider client resolution does not apply user-configured default_headers, causing failures with referer-restricted API keys. A fix propagates those headers to the native Gemini fallback clients.

Open issues1

  • Issue#102788`resolve_provider_client` gemini-native path ignores user default_headers — fallback dies on referer-restricted keys

Open PRs2

  • PR#102794fix(agent): honor model.default_headers on the gemini-native fallback path
  • PR#107953fix(gemini): apply user default_headers to native-Gemini fallback clients (#102788)
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

Subsystem
agent
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/102788.json
cluster/102788.md