NousResearch/hermes-agent

Fallback provider extra_body not forwarded to requests

Cluster 26460 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
5items grouped
Known?
Yes. 5 related items grouped here, 0 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 1 PR.

These issues and fixes concern a bug where extra_body metadata from fallback provider entries was not being passed through to the active request path during fallback activation. Multiple fix attempts address forwarding this field correctly.

Open issues1

  • Issue#26460[Bug]: OpenRouter fallback entry ignores fallback-local provider routing metadata

Open PRs1

  • PR#55892fix(agent): forward fallback_providers[].extra_body into the active request path (#26460)

3 PRs closed without merging

From the close comments: duplicate 2 · stale or abandoned 1

  • #26483 fix(agent): forward fallback_providers[].extra_body during fallback activation (#26460) · stale or abandoned
  • #26492 fix(fallback): forward extra_body from fallback entries to request path · duplicate → #26483, #26460
  • #26517 fix(agent): honor fallback provider extra body · duplicate → #55892
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
3 PRs closed without merging

For your agent

The same facts, typed.