Cairn
NousResearch/hermes-agent

Provider routing propagation for custom providers

Cluster 24450 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

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

These issues and PRs concern forwarding and preserving provider routing preferences when using custom providers. The work spans multiple request paths and transport layers to ensure routing configuration is correctly propagated.

Open issues1

  • Issue#24450Support `provider` routing for custom providers (e.g. Polza.ai)

Open PRs1

  • PR#72643fix(custom): forward provider routing prefs via the profile path

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #24542 fix(transports): propagate provider routing prefs to custom providers · superseded by another PR → #72643
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.67: 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
1 PR closed without merging

For your agent

The same facts, typed.

cluster/24450.json
cluster/24450.md