Cairn

Configurable block recurrence limit and kanban fixes

NousResearch/hermes-agent · cluster 59333 · cron

Data as of

9 open items. Fix attempted, not merged.

The short answer

2open issues
7open PRs
9items grouped
Known?
Yes. 9 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
2 issues and 7 PRs.

These items cover making the block recurrence/repeat limit configurable via settings or environment variables, plus several kanban-specific fixes around pass-loop state persistence, dependency guard logic, and repeated failure handling.

Open issues2

  • Issue#59333[Feature]: Use config for BLOCK_RECURANCE_LIMIT
  • Issue#66909[Feature]: Please allow to modify BLOCK_RECURRENCE_LIMIT

Open PRs7

  • PR#59367feat(kanban): make block recurrence limit configurable
  • PR#59536feat(kanban): make block recurrence limit configurable
  • PR#59645feat(cron): make BLOCK_RECURANCE_LIMIT configurable (#59333)
  • PR#60476feat(cron): add configurable max_repeat safeguard for cron job repeats (#59333)
  • PR#63723fix(kanban): persist pass-loop state on task rows
  • PR#66632fix(kanban): guard dependency block after successor creation
  • PR#68027fix(kanban): freeze repeated identical failures
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.32: 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
cron
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/59333.json
cluster/59333.md