Cairn
NousResearch/hermes-agent

Feishu multiplex DM admission and profile isolation fixes

Cluster 86905 · gateway. Data as of

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

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 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.

A bug and related fixes addressing how DM allow-list and allow-all admission settings are looked up per-profile under Feishu multiplexed configurations. The work also covers keeping separate WebSocket loops and admission gates per profile, and handling cloned app credential rejection.

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

1 PR closed without merging

From the close comments: merged via another change 1

  • #86908 fix(feishu): resolve DM admission config per-profile under multiplex (#86905) · merged via another change → 14f20d1, #101251
Closed issues · 1
  • Closed#86905[Bug] Feishu multiplex: DM allow-list and allow-all flags ignore profile-scoped .env — role-bot DMs silently rejected (dm_policy_rejected)
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

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

For your agent

The same facts, typed.

cluster/86905.json
cluster/86905.md