Cairn
NousResearch/hermes-agent

Webhook session context and delivery visibility work

Cluster 112274 · gateway. Data as of

Nothing open on GitHub. Fix merged in #120825 on 24 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 #120825. 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.

These items concern making webhook delivery sessions identifiable by route, allowing replies to see delivered content via an opt-in mirror, and bridging webhook context so DM sessions can reference incoming webhook messages.

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.

  • #120825 feat(webhook): replies to a webhook delivery can see what was delivered (opt-in mirror_to_session, salvage #106067)

    merged to main

    files: contributors/emails/[redacted:email], gateway/platforms/webhook.py, hermes_cli/subcommands/webhook.py, hermes_cli/webhook.py, skills/autonomous-ai-agents/hermes-agent/references/webhooks.md, tests/gateway/test_webhook_adapter.py, website/docs/reference/cli-commands.md, website/docs/user-guide/messaging/webhooks.md

2 PRs closed without merging

From the close comments: closed without comment 1 · done elsewhere 1

  • #112297 fix(gateway): bridge webhook context to configured DMs · done elsewhere → 64ae570, #112274, #120825, #106067
  • #112660 feat(webhook): name each delivery session after its route so any session can resolve it · closed without comment
Closed issues · 1
  • Closed#112274Webhook sessions are context-siloed — DM session can't reference the message that just arrived
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
#120825
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
24 Sep 2026

For your agent

The same facts, typed.

cluster/112274.json
cluster/112274.md