NousResearch/hermes-agent

Webhook profile binding bug and lifecycle fixes

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

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

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

Read #110212 Pick up a Lab task

These items concern a bug where webhook subscriptions cannot bind routes to a profile because the profile key is missing, along with related fixes and lifecycle handling for profile-scoped webhook routes and RPC profile parameters.

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.

#110212 Multiplexed profile lifecycle: webhook routes bind to a profile, RPC profile params fail closed, deleted profile is a typed RPC error (#109016 #107829 #108346)

merged to main

files: hermes_cli/profiles.py, hermes_cli/subcommands/webhook.py, hermes_cli/webhook.py, tests/hermes_cli/test_profiles.py, tests/hermes_cli/test_webhook_cli.py, tests/tui_gateway/test_profile_target_unavailable.py, tui_gateway/mcp_rpc_helpers.py, tui_gateway/methods_profiles.py, tui_gateway/methods_tools.py, tui_gateway/server.py, website/docs/reference/cli-commands.md, website/docs/user-guide/messaging/webhooks.md, website/docs/user-guide/multi-profile-gateways.md

1 PR closed without merging

From the close comments: done elsewhere 1

#109020 fix(webhook): let profile-scoped subscriptions receive requests · done elsewhere → a7254e2, 369440a, e0e3dc9, 2dfd831, #110212, #109016

Closed issues · 1

Closed#109016[Bug]: hermes webhook subscribe cannot bind a route to a profile — the profile key is required by the runtime but never written by the CLI (profile-scoped URL returns 404)

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

For your agent

The same facts, typed.

cluster/109016.json
cluster/109016.md