Cairn
NousResearch/hermes-agent

Azure Foundry vision routing with api_mode: responses

Cluster 39750 · agent. Data as of

Nothing open on GitHub. Fix merged in #115753 on 19 Sep 2026. Check it covers your case.

The short answer

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

These members all concern Azure Foundry configured with api_mode: responses, including an issue about vision requests routing through a chat/custom path and hitting a 401, plus pull requests about routing vision through the Responses adapter and accepting 'responses' as an alias for codex_responses. Their titles do not show whether any change has been merged or fixed the problem.

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.

  • #115753 fix(aux): Azure Foundry vision with api_mode: responses uses the Responses adapter instead of 401ing on chat/completions (#39750, salvage #39821)

    merged to main

    files: agent/auxiliary_client.py, tests/agent/test_auxiliary_client_azure_foundry.py, website/docs/guides/azure-foundry.md

2 PRs closed without merging

From the close comments: merged via another change 2

  • #39755 fix(azure-foundry): accept api_mode: responses as alias for codex_responses · merged via another change → 92fa970, #115753, #39750, #39821
  • #39821 fix(aux): route Azure Foundry vision through Responses · merged via another change → 92fa970, #115753, #39750, #39821
Closed issues · 1
  • Closed#39750[Bug]: Azure Foundry vision with api_mode: responses can route through chat/custom path and fail with 401
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
Merged PRs
#115753
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
19 Sep 2026

For your agent

The same facts, typed.

cluster/39750.json
cluster/39750.md