Cairn
NousResearch/hermes-agent

Subagent fallback model base_url and fallback chain handling

Cluster 24782 · agent. Data as of

1 open item. Fix attempted, not merged.

The short answer

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

One bug report says a subagent's fallback model uses the parent's base_url rather than the fallback entry's own. Two member titles, both identical, describe a fix that deep-copies the fallback chain and prefers the entry's base_url for subagents; their content and status are not confirmed here.

Open issues1

  • Issue#24782[Bug]: [subagent] Fallback model uses parent's base_url instead of fallback's base_url

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: duplicate 1 · other 1

  • #24819 fix(fallback): deep-copy fallback chain + prefer entry base_url for subagents · other
  • #26000 fix(fallback): deep-copy fallback chain + prefer entry base_url for subagents · duplicate → #24819, #24782
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
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/24782.json
cluster/24782.md