# NousResearch/hermes-agent · WeCom WebSocket CLOSING state CPU spin fix

## Open now

- Nothing open on GitHub.

These members address a bug where the WeCom gateway enters a CPU spin when a WebSocket connection reaches the CLOSING state. The fix adds handling for WSMsgType.CLOSING to prevent this behavior.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #28311. Verify it addresses your case.
- **Recommended:** read PR #28311 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-28311`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #28293: fix(gateway): WeCom gateway CPU spin when WebSocket enters CLOSING state

## Prior & competing PRs

- **#28311: fix(wecom): handle WSMsgType.CLOSING to prevent CPU spin (#28286)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `gateway/platforms/wecom.py`
- **#28286: fix(wecom): handle WSMsgType.CLOSING to prevent CPU spin**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `8dca28775ef03841744563e7b5bc15839ae3d807`, `#28311`

## Fix status

- Merged to main in PR #28311 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-05-19`.