Status command misreports messaging platforms as configured
Cluster 96190. Data as of
Nothing open on GitHub. Fix merged in #131217 on 2 Oct 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #131217. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #131217. That is separate from the fix event. - Still open
- Nothing open on GitHub.
The status command incorrectly reports messaging platform plugins as configured when only commented-out example environment variable lines are present. These members address detecting and fixing how credential chain presence is evaluated for status reporting.
Open issues0
Open PRs0
Fixes on record
-
#131217 hermes status --full lists each messaging platform once, with the summary's verdict (#96190)
files:
hermes_cli/status.py,tests/hermes_cli/test_status.py,website/docs/developer-guide/adding-platform-adapters.md
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#96200 fix(status): plugin platforms report configured via the credential chain · superseded by another PR →
25aa38c,#131217
Closed issues · 1
- Closed#96190hermes status reports messaging platforms as "configured (plugin)" with only commented-out example .env lines present
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.00means 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 LabAt a glance
- Merged PRs
- #131217
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 2 Oct 2026