Cairn
NousResearch/hermes-agent

kanban max_in_progress config and CLI passthrough

Cluster 33488 · hermes cli. 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, 1 issue 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
Nothing open on GitHub.

These items cover adding a max_in_progress option to cap concurrent kanban tasks and fixing the CLI dispatch command to correctly pass that configuration through to dispatch_once.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: closed without comment 1 · duplicate 1

  • #33556 fix(kanban): honor max_in_progress in CLI dispatch · closed without comment
  • #33646 fix(kanban): pass max_in_progress from CLI dispatch to dispatch_once · duplicate → #33556, #33488
Closed issues · 1
  • Closed#33488[Bug]: hermes kanban dispatch command doesn't pass max_in_progress to dispatch_once
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
hermes cli
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/33488.json
cluster/33488.md