Cairn
NousResearch/hermes-agent

Bug fix: max_spawn_depth=0 coerced to 1 silently

Cluster 91765 · 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.

A bug caused max_spawn_depth=0 to be silently overridden to 1, preventing users from fully disabling subagent spawning. These items track the report and fix for that coercion behavior.

Open issues1

  • Issue#91765delegation.max_spawn_depth: 0 is silently coerced to 1, can't fully disable subagent spawning

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: duplicate 2

  • #91772 fix: max_spawn_depth=0 no longer silently coerced to 1 · duplicate
  • #91970 fix(tools): allow max_spawn_depth=0 to disable subagent spawning (#91765) · duplicate → #91772
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/91765.json
cluster/91765.md