Cairn
NousResearch/hermes-agent

Feishu app credentials missing from multiplex fingerprint

Cluster 76793 · gateway. Data as of

Nothing open on GitHub. Fix merged in #101251. Check it covers your case.

The short answer

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

The Feishu app_id and secret are not included in the credential fingerprint used for multiplex conflict detection, causing cloned profiles sharing one app to spawn competing WebSocket clients. Multiple fixes address adding these fields to the fingerprint logic.

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.

  • #101251 fix(feishu): multiplexed profiles keep their own WS loop and admission gates; cloned app credentials refused (#73779 #76793 #86905, salvage #76800 #86908 #84165)

    merged to main

    files: gateway/run.py, plugins/platforms/feishu/adapter.py, tests/gateway/feishu_helpers.py, tests/gateway/test_feishu_bot_admission.py, tests/gateway/test_feishu_ws_multiplex_isolation.py, tests/gateway/test_multiplex_adapter_registry.py

3 PRs closed without merging

From the close comments: merged via another change 2 · done elsewhere 1

  • #76800 fix(feishu): fingerprint app credentials for multiplex guard (#76793) · merged via another change → 14f20d1, #101251
  • #76802 fix(gateway): fingerprint Feishu app_id for multiplex conflict detection · done elsewhere
  • #76803 fix(gateway): add Feishu _app_id to multiplex credential fingerprint (#76793) · merged via another change → 14f20d1, #101251, #76800
Closed issues · 1
  • Closed#76793Feishu multiplex: app_id/secret credential invisible to _adapter_credential_fingerprint — cloned profiles spawn competing WebSocket clients for one app, connection loop kicks all offline
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.40: 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

Subsystem
gateway
Merged PRs
#101251
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
2 Sep 2026

For your agent

The same facts, typed.

cluster/76793.json
cluster/76793.md