NousResearch/hermes-agent

Azure Foundry provider routing, auth header, and API mode issues

Cluster 46821 · agent. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR 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 2 PRs.

These members all concern Azure Foundry support: one bug report describes dropped query parameters and an unintended API mode upgrade, while the others are fixes touching endpoint routing, the api-key auth header on OpenAI-wire routes, and routing vision through Responses. The titles don't confirm whether any of these changes are merged or effective.

Open issues1

  • Issue#46821bug: Azure Foundry provider drops query parameters and incorrectly upgrades API mode

Open PRs2

  • PR#46825fix: correct Azure Foundry endpoint routing and API mode
  • PR#63312fix(auth): send Azure api-key header on OpenAI-wire routes

1 PR closed without merging

From the close comments: merged via another change 1

  • #39821 fix(aux): route Azure Foundry vision through Responses · merged via another change → 92fa970, #115753, #39750, #39821
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
1 PR closed without merging

For your agent

The same facts, typed.