Cairn
NousResearch/hermes-agent

Fix webhook/gateway replies routing to wrong profile

Cluster 65939 · gateway. Data as of

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

The short answer

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

These issues and fixes address a bug where webhook replies and gateway callbacks are delivered through the wrong profile's adapter instead of the originating profile. The changes ensure reply routing stays scoped to the correct profile context.

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.

  • #107626 fix(gateway): /p/<profile>/ webhook replies and api_server callbacks stay on the routed profile (#65939, #84266, salvage #65944/#103041/#67147)

    merged to main

    files: gateway/platforms/api_server.py, gateway/platforms/webhook.py, tests/gateway/test_webhook_adapter.py, tests/gateway/test_webhook_deliver_only.py, tests/gateway/test_webhook_integration.py, tests/gateway/test_webhook_profile_egress.py, website/docs/user-guide/multi-profile-gateways.md

2 PRs closed without merging

From the close comments: superseded by another PR 2

  • #65944 fix(webhook): preserve profile-scoped reply delivery · superseded by another PR → c3e01c7, #107626, #65939
  • #65957 fix(webhook): use profile-specific adapter and home channel for reply delivery · superseded by another PR → c3e01c7, #107626, #65944, #65939
Closed issues · 1
  • Closed#65939Profiled webhooks can send replies through the wrong 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.50: 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
#107626
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
11 Sep 2026

For your agent

The same facts, typed.

cluster/65939.json
cluster/65939.md