NousResearch/hermes-agent

Gateway probe scoping fixes across dashboard pages

Cluster 71211. Data as of 2026-10-25 11:21 UTC

Nothing open on GitHub. Fix merged in #72029 on 26 Jul 2026. Check it covers your case.

open issues

open PRs

items grouped

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

Next step: read #72029, then check it covers your case.

Read #72029 Pick up a Lab task

A bug and related fixes addressing gateway state reads being incorrectly scoped to the default profile instead of the active profile's home, affecting the channels page, Kanban dispatcher, and dashboard status indicators.

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.

#72029 fix(dashboard): one gateway liveness ladder for status + channels

merged to main

files: gateway/status.py, hermes_cli/kanban.py, hermes_cli/web_server.py, plugins/kanban/dashboard/plugin_api.py, tests/gateway/test_status.py, tests/hermes_cli/test_web_server.py, tests/hermes_cli/test_web_server_messaging_profiles.py, tests/plugins/test_kanban_dashboard_plugin.py

2 PRs closed without merging

From the close comments: done elsewhere 2

#71258 fix(web): scope messaging/kanban gateway probes to profile home · done elsewhere → 6179da5, #72029, #71211
#71261 fix(gateway): scope channels page gateway status reads to profile (#71211) · done elsewhere → #71211, #72029

Closed issues · 1

Closed#71211[Bug]: Channels page and Kanban dispatcher probe still read the default profile's gateway state (same root cause as #69143)

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: #72029
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 26 Jul 2026

For your agent

The same facts, typed.

cluster/71211.json
cluster/71211.md