# NousResearch/hermes-agent · Kanban max in-progress task limit configuration

## Open now

- Nothing open on GitHub.

All three members concern limiting how many Kanban tasks can be in progress or running concurrently, via a max_in_progress config option. They include a feature request and two items with the same feature title, one referencing #22981.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #28420. Verify it addresses your case.
- **Recommended:** read PR #28420 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

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

- #22829: \[Feature\]: Kanban system tasks limit for  in progress

## Prior & competing PRs

- **#28420: feat(kanban): add max_in_progress config to cap concurrent running tasks (#22981)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `gateway/run.py`, `hermes_cli/kanban_db.py`, `tests/hermes_cli/test_kanban_db.py`
- **#22981: feat(kanban): add max_in_progress config to cap concurrent running tasks**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#28420`

## Fix status

- Merged to main in PR #28420 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-05-19`.
- Subsystem: `cron`