Cairn
NousResearch/hermes-agent

Azure/custom API key header name support

Cluster 63303 · agent/secret sources. Data as of

2 open items. Fix attempted, not merged.

The short answer

0open issues
2open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue 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
0 issues and 2 PRs.

These issues and PRs address the inability to configure or send a custom API key header name, particularly for Azure and Azure Foundry endpoints. Work includes bug reports and fixes for sending the correct auth header on Azure and custom provider routes.

Open issues0

No open issues.

Open PRs2

  • PR#63312fix(auth): send Azure api-key header on OpenAI-wire routes
  • PR#63313fix(auth): add azure api-key headers

1 PR closed without merging

From the close comments: done elsewhere 1

  • #63909 fix(providers): add api_key_header config option for custom auth header name · done elsewhere → b98baa3, #63303
Closed issues · 1
  • Closed#63303[Bug]: azure foundry api no configuration option to override header name
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/secret sources
Closed issues
1
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/63303.json
cluster/63303.md