Cairn
NousResearch/hermes-agent

Webhook env vars ignored when enabled via config.yaml

Cluster 119763. Data as of

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

These issues and PRs address a bug where WEBHOOK_SECRET and WEBHOOK_PORT environment variables are not applied when the webhook platform is enabled through config.yaml rather than environment variables. The work involves fixing gateway config handling to ensure env var references expand correctly for webhook and platform settings.

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.

  • #120072 gateway config: env refs expand for platforms.* and WEBHOOK_SECRET/PORT apply to a yaml-enabled webhook (#119733 #119763; salvage #119755/#119765, supersede #119737 #119750 #119770)

    merged to main

    files: gateway/config_env.py, gateway/config_loader.py, tests/gateway/test_config.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

  • #119765 fix(gateway): bridge webhook env settings for config enablement · merged via another change → 004fa2e, #120072
  • #119770 fix(gateway): apply WEBHOOK_SECRET/WEBHOOK_PORT when webhook is enabled via config.yaml · done elsewhere → 004fa2e, #119765, #120072
Closed issues · 1
  • Closed#119763[Bug]: Webhook env vars (WEBHOOK_SECRET/WEBHOOK_PORT) are ignored when the platform is enabled via config.yaml
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

Merged PRs
#120072
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
23 Sep 2026

For your agent

The same facts, typed.

cluster/119763.json
cluster/119763.md