NousResearch/hermes-agent

Kanban served-profile api_server session wake scoping fix

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

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

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

Read #114820 Pick up a Lab task

These items concern a bug where the wake signal for a served profile's api_server session under multiplexing is delivered in the wrong scope or skipped entirely. The work addresses ensuring the wake occurs in-process under the correct profile's own scope.

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.

#114820 fix(kanban): served profile's api_server session wake is delivered in its own scope under multiplex (#114679, salvage #114680)

merged to main

files: contributors/emails/[redacted:email], gateway/kanban_watchers_notifier.py, gateway/platforms/api_server.py, gateway/platforms/api_server_runs.py, gateway/run_notifications.py, gateway/wake.py, tests/gateway/test_background_process_served_apiserver_wake.py, tests/gateway/test_kanban_notifier_served_apiserver_wake.py, website/docs/user-guide/features/kanban.md

1 PR closed without merging

From the close comments: merged via another change 1

#114680 fix(kanban): wake a served profile's api_server session in-process under its own scope · merged via another change → 66d7931, #114820, #114679, #114680

Closed issues · 1

Closed#114679Multiplexed served-profile api_server Kanban completion wake is skipped (raw-session subscription fails closed; the self-post would land in the default profile)

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

For your agent

The same facts, typed.

cluster/114679.json
cluster/114679.md