Cairn
NousResearch/hermes-agent

api_mode config ignored or hardcoded incorrectly

Cluster 33600 · agent. Data as of

3 open items. Fix attempted, not merged.

The short answer

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

These members address a bug where api_mode from config.yaml is not respected for custom providers, and related refactoring to tie api_mode to provider config and clear it properly on provider switches.

Open issues1

  • Issue#33600provider: custom always appends /chat/completions to base_url, ignoring api_mode

Open PRs2

  • PR#33604fix(custom): normalize responses api mode alias
  • PR#33889feat: add api_mode=responses for generic OpenAI Responses API (#33600)

3 PRs closed without merging

From the close comments: superseded by another PR 1 · other 2

  • #33637 fix: accept responses as alias for codex_responses in api_mode config · superseded by another PR → #33604
  • #33765 fix(provider): custom provider respects api_mode and works in cron/bg tasks (#33600, #33333) · other → #33604, #33637, #33347, #33339
  • #33884 feat: Prometheus — CommandCode provider, api_mode=responses, goal migration, Honcho prune, profile routing · other → #33886, #33889, #33888, #33890, #33891, #33892, #33893, #32909, #33620, #29955, #18749, #18427, #33558, #33604, #33637, #33765
Closed issues · 2
  • Closed#65031Custom provider api_mode from config.yaml is ignored — always uses chat_completions
  • Closed#68159custom_providers + api_mode: anthropic_messages silently routes to /v1/chat/completions instead of /v1/messages — usage.input_tokens always 0
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.20: 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
2
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/33600.json
cluster/33600.md