Cairn
NousResearch/hermes-agent

Kanban blocked/crashed task push notifications

Cluster 22995 · cron. 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 members concern adding push notification support to alert a configured channel when a Kanban task transitions to a blocked or crashed state. The work spans a feature request and at least two implementation efforts addressing the same notification behavior.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: stale or abandoned 1 · superseded by another PR 1

  • #23120 feat(kanban): push notification when a task transitions to blocked · stale or abandoned
  • #24286 feat(kanban): notify configured channel on task block/crash · superseded by another PR → #23120
Closed issues · 1
  • Closed#22995[Feature]: Kanban — push notification on task block/crash
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
cron
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/22995.json
cluster/22995.md