NousResearch/hermes-agent

custom: prefix stripped in auxiliary provider routing

Cluster 13762 · agent. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
10items grouped
Known?
Yes. 10 related items grouped here, 3 issues already closed.
Fix event
No fix has been merged to main. 7 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

Multiple reports and fixes address a bug where the 'custom:' prefix is incorrectly stripped or rewritten during auxiliary (vision, codex) provider resolution, causing custom providers to be misidentified as built-in ones. The fixes aim to preserve the prefix through normalization and routing logic.

Open issues0

No open issues.

Open PRs0

No open pull requests.

7 PRs closed without merging

From the close comments: done elsewhere 3 · superseded by another PR 2 · duplicate 1 · other 1

  • #13781 fix(auxiliary): preserve 'custom:' prefix in _normalize_aux_provider (Closes #13762) · done elsewhere → cbf1f15, #5978
  • #17498 fix(agent): preserve custom codex provider aliases · done elsewhere → 0ddc8ab
  • #17504 fix(agent): preserve explicit custom:codex auxiliary routing · other → #17498, #17488
  • #44361 fix(auxiliary): preserve custom: prefix in vision provider resolution · superseded by another PR → #13781
  • #44363 fix: preserve custom: prefix in _normalize_aux_provider for named custom providers · done elsewhere → 0ddc8ab
Show 2 more
  • #44398 fix(agent): resolve custom: prefix in vision provider before normalisation · duplicate → #13781
  • #44520 fix(agent): preserve custom: prefix in vision provider resolution (#44349) · superseded by another PR → #13781, #44349
Closed issues · 3
  • Closed#13762Bug: custom_providers not working with auxiliary tasks — custom: prefix stripped by _normalize_aux_provider
  • Closed#17488custom provider named codex is rewritten to openai-codex in auxiliary paths
  • Closed#44349auxiliary.vision.provider="custom:xxx" collapses to bare built-in, ignores custom_providers (causes 401)
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.19: 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
3
Attempts
7 PRs closed without merging

For your agent

The same facts, typed.