Cairn
NousResearch/hermes-agent

Fallback provider chain inheritance in delegated subagents

Cluster 7481 · agent. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 2 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
Nothing open on GitHub.

These items concern whether subagents spawned via delegate_task inherit the parent's fallback_providers configuration, including a feature request for per-delegation control and a test case to cover this behavior.

Open issues0

No open issues.

Open PRs0

No open pull requests.

1 PR closed without merging

From the close comments: other 1

  • #49477 test(delegation): cover fallback-chain inheritance under a pinned subagent base_url · other → #80465, #105347
Closed issues · 2
  • Closed#7481Feature request: per-delegation fallback provider chain
  • Closed#49417Subagents dispatched via `delegate_task` do not inherit parent's `fallback_providers` chain
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.45: 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
1 PR closed without merging

For your agent

The same facts, typed.

cluster/7481.json
cluster/7481.md