# NousResearch/hermes-agent · kanban max_in_progress config and CLI passthrough

## Open now

- 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.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #33488: \[Bug\]: hermes kanban dispatch command doesn't pass max_in_progress to dispatch_once

## Prior & competing PRs

- **#33556: fix(kanban): honor max_in_progress in CLI dispatch**. closed without merge
  - maintainer direction: category `silent_close`; implication `active`
- **#33646: fix(kanban): pass max_in_progress from CLI dispatch to dispatch_once**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#33556`, `#33488`

## Fix status

- No merged fix on record.
- Subsystem: `hermes_cli`