Cairn
NousResearch/hermes-agent

Oneshot mode ignores max_iterations setting

Cluster 99957 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
4items grouped
Known?
Yes. 4 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 1 PR.

A bug where the oneshot/-z CLI path errors by not passing the computed max_iterations value to AIAgent. Multiple fix attempts address this missing argument in the oneshot code path.

Open issues1

  • Issue#99957[Bug]: -z (oneshot) ignores agent.max_turns and HERMES_MAX_ITERATIONS — max_iterations never passed to AIAgent

Open PRs1

  • PR#99994fix(cli): pass max_iterations to AIAgent in oneshot path

2 PRs closed without merging

From the close comments: duplicate 1 · superseded by another PR 1

  • #99976 fix(cli): pass resolved max_iterations to AIAgent in oneshot mode · superseded by another PR → #61152, #99957
  • #100770 fix(oneshot): pass resolved max_iterations to AIAgent (#99957) · duplicate → #61152
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.50: 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
hermes cli
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/99957.json
cluster/99957.md