Cairn
NousResearch/hermes-agent

Vertex AI provider registration and auth fixes

Cluster 69231 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

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

These items relate to Google Vertex AI not being properly registered in provider/auth registries, causing failures with Gemini models and auxiliary clients. Fixes and a bug report address registration in PROVIDER_REGISTRY, HERMES_OVERLAYS, and related auth error messaging.

Open issues1

  • Issue#69231[Bug] Google Vertex AI Provider Fails with Gemini Models (HTTP 400: INVALID_ARGUMENT), while LiteLLM Proxy Access Succeeds

Open PRs1

  • PR#61933fix(auth): register vertex in PROVIDER_REGISTRY for auxiliary clients

2 PRs closed without merging

From the close comments: merged via another change 1 · other 1

  • #56688 fix(vertex,moa): register vertex in PROVIDER_REGISTRY and HERMES_OVERLAYS · merged via another change → 9b868f6, #70282
  • #56842 fix(agent): clarify auxiliary provider auth failures · other
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

Subsystem
agent
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/69231.json
cluster/69231.md