NousResearch/hermes-agent

Desktop status bar conflates two connection states

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

Nothing open on GitHub. Fix merged in #132018 on 5 Oct 2026. Check it covers your case.

open issues

open PRs

items grouped

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

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

Read #132018 Pick up a Lab task

The desktop app's status indicator shows 'Gateway Ready' based on backend connection alone, without reflecting the messaging gateway's actual health. These items address distinguishing between backend connectivity and messaging-gateway status in the UI.

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.

#132018 fix(desktop): distinguish backend connection from messaging-gateway health [risk 0.65]

merged to main

files: apps/desktop/src/app/shell/hooks/use-statusbar-items.tsx, apps/desktop/src/i18n/ar_chrome.ts, apps/desktop/src/i18n/en.ts, apps/desktop/src/i18n/ja.ts, apps/desktop/src/i18n/ru.ts, apps/desktop/src/i18n/types.ts, apps/desktop/src/i18n/zh-hant_chrome.ts, apps/desktop/src/i18n/zh.ts, apps/desktop/src/lib/gateway-health-pill.test.ts, apps/desktop/src/lib/gateway-health-pill.ts, locales/_keys.desktop.json

1 PR closed without merging

From the close comments: merged via another change 1

#103902 fix(desktop): distinguish backend connection from messaging-gateway health · merged via another change → #132018

Closed issues · 1

Closed#102975[Bug/UX]: Desktop status bar shows "Gateway Ready" while the Discord messaging gateway is down — pill reflects chat-backend connection only

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

Merged PRs: #132018
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 5 Oct 2026

For your agent

The same facts, typed.

cluster/102975.json
cluster/102975.md