NousResearch/hermes-agent

Feishu WebSocket mid-life disconnect detection and recovery

Cluster 113662. Data as of 2026-10-26 12:29 UTC

Nothing open on GitHub. Fix merged in #114855 on 18 Sep 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 #114855. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #114855. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #114855 Pick up a Lab task

These items address a bug where a mid-life Feishu WebSocket connection loss was undetectable because the lark-oapi start() call never returns, preventing worker-exit detection from firing. The fixes stop the worker loop on SDK receive-loop death and rebuild lost connections.

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.

#114855 fix(feishu): a websocket link lost mid-life is detected and rebuilt (#113662, salvage #113668)

merged to main

files: plugins/platforms/feishu/adapter.py, tests/gateway/test_feishu.py, tests/gateway/test_feishu_profile_scope_hops.py, tests/gateway/test_feishu_ws_multiplex_isolation.py, website/docs/user-guide/messaging/feishu.md

1 PR closed without merging

From the close comments: merged via another change 1

#113668 fix(feishu): stop the WS worker loop when the SDK receive loop dies · merged via another change → 0d0ccb8, #114855, #113662, #113668

Closed issues · 1

Closed#113662[Bug]: Feishu WS mid-life loss is undetectable — lark-oapi start() never returns, so worker-exit detection can never fire

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: #114855
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 18 Sep 2026

For your agent

The same facts, typed.

cluster/113662.json
cluster/113662.md