Kanban max in-progress task limit configuration
Cluster 22829 · cron. Data as of
Nothing open on GitHub. Fix merged in #28420 on 19 May 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #28420. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 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.
Open issues0
Open PRs0
Fixes on record
-
#28420 feat(kanban): add max_in_progress config to cap concurrent running tasks (#22981)
files:
gateway/run.py,hermes_cli/kanban_db.py,tests/hermes_cli/test_kanban_db.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#22981 feat(kanban): add max_in_progress config to cap concurrent running tasks · merged via another change →
#28420
Closed issues · 1
- Closed#22829[Feature]: Kanban system tasks limit for in progress
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.00means 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 LabAt a glance
- Subsystem
- cron
- Merged PRs
- #28420
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 19 May 2026