NousResearch/hermes-agent

Kanban block-loop notification wording corrections

Cluster 111125. Data as of

Nothing open on GitHub. Fix merged in #111395 on 15 Sep 2026. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #111395. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #111395. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items address misleading language in block-loop triage notifications that incorrectly implied a human or owner decision was required. Changes focus on clarifying and neutralizing the wording of those automated pings.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #111395 fix(kanban): block-loop triage pings no longer claim a human decision unless the block is needs_input (#111125, salvage #111132)

    merged to main

    files: apps/desktop/src/plugins/kanban/completion-notify.test.ts, apps/desktop/src/plugins/kanban/completion-notify.ts, apps/desktop/src/plugins/kanban/i18n.ts, gateway/kanban_watchers_notifier.py, hermes_cli/kanban.py, locales/af.yaml, locales/ar.yaml, locales/de.yaml, locales/en.yaml, locales/es.yaml, locales/fr.yaml, locales/ga.yaml, locales/hu.yaml, locales/it.yaml, locales/ja.yaml, locales/ko.yaml, locales/pt.yaml, locales/ru.yaml, locales/tr.yaml, locales/uk.yaml (+4 more)

2 PRs closed without merging

From the close comments: merged via another change 1 · other 1

  • #111131 fix(kanban): clarify block loop notifications · other → 57e43e1, 0daa181, #111131, #111125, #111132
  • #111132 fix(gateway): neutral orchestration wording for block-loop triage pings · merged via another change → #111395, #111131
Closed issues · 1
  • Closed#111125Kanban block-loop notifications falsely claim that an owner decision is required
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.50: 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

Merged PRs
#111395
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
15 Sep 2026

For your agent

The same facts, typed.