Cairn

Azure Foundry GPT-6 Luna/Sol Responses API routing

NousResearch/hermes-agent · cluster 120263 · agent

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
5items grouped
Known?
Yes. 5 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 2 PRs.

A bug report and two related fix attempts addressing the need to route Azure Foundry GPT-6 Luna and Sol models to the Responses API when function tools and reasoning are enabled.

Open issues1

  • Issue#120263[Bug] Azure Foundry gpt-6-luna requires Responses API when function tools and reasoning are enabled

Open PRs2

  • PR#139489fix(azure-foundry): route gpt-6 to Responses and honour a caller's explicit api_mode
  • PR#142809GPT-6 behind Azure Foundry or a custom gateway no longer 400s on max_tokens or temperature (port cline#15137, salvage #135527 #67846)

2 PRs closed without merging

From the close comments: done elsewhere 1 · duplicate 1

  • #120327 fix(azure-foundry): route GPT-6 Luna/Sol to Responses API · done elsewhere
  • #124105 fix(azure-foundry): route GPT-6 Luna/Sol to the Responses API · duplicate → 0e427d7, #120327, #120263
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

Subsystem
agent
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/120263.json
cluster/120263.md