Cairn
NousResearch/hermes-agent

Gemini auth header conflict causing HTTP 400 errors

Cluster 7893. Data as of

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

The short answer

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

A bug where requests to the native Gemini provider sent both Authorization: Bearer and x-goog-api-key headers simultaneously, triggering HTTP 400 'Multiple authentication credentials' errors. Multiple fix attempts address routing auth through the correct x-goog-api-key header only.

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.

  • #11961 fix(gemini): route Google AI Studio auth via x-goog-api-key header (#7893)

    merged to main

    files: agent/auxiliary_client.py, run_agent.py, scripts/release.py, tests/hermes_cli/test_gemini_provider.py

3 PRs closed without merging

From the close comments: superseded by another PR 2 · merged via another change 1

  • #8172 fix(gemini): use x-goog-api-key header to prevent dual-auth 400 error · superseded by another PR → #11961, #8530
  • #8530 fix: suppress Authorization: Bearer for Gemini provider to prevent HT… · merged via another change → #11961, #11472
  • #9247 fix(gemini): use x-goog-api-key header instead of Bearer token · superseded by another PR → #11961, #8530
Closed issues · 1
  • Closed#7893[Bug]: HTTP 400 "Multiple authentication credentials received" when using native gemini provider
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.40: 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
#11961
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
18 Apr 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.

For your agent

The same facts, typed.

cluster/7893.json
cluster/7893.md