NousResearch/hermes-agent

Gateway wake admission conflicts in shared Discord threads

Cluster 143306 · gateway. Data as of 2026-10-27 11:58 UTC

Nothing open on GitHub. Fix merged in #143590 on 25 Oct 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 #143590. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #143590 Pick up a Lab task

A bug report describes shared Discord thread speaker changes leaving pinned completion wakes stuck with admission_conflict, and two gateway fix PRs address wake admission after speaker changes and based on route identity rather than display fields. The titles suggest a shared theme around wake admission logic, but the details of the changes are not visible from titles alone.

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.

#143590 fix(gateway): admit automation wakes on route identity, not display fields

merged to main

files: gateway/run_notifications_ownership.py, gateway/session_automation.py, gateway/session_ingress_context.py, tests/gateway/test_automation_notification_category.py, tests/gateway/test_automation_wake_route.py

1 PR closed without merging

From the close comments: superseded by another PR 1

#143307 fix(gateway): admit thread wakes after the speaker changes · superseded by another PR → d49e2eb, #143590, #143306

Closed issues · 1

Closed#143306[Bug]: Shared Discord thread speaker changes strand pinned completion wakes with admission_conflict

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: #143590
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 25 Oct 2026

For your agent

The same facts, typed.

cluster/143306.json
cluster/143306.md