Cairn
NousResearch/hermes-agent

Top-level platform config keys not reaching adapter extra

Cluster 10206 · gateway. Data as of

1 open item. Fix merged in #109173 on 12 Sep 2026. Check it covers your case.

The short answer

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

Members describe platform settings in config.yaml, such as webhook port or api_server host/port/key, being ignored when placed directly under the platform instead of under extra. Most are proposed fixes that forward or merge those top-level keys into config.extra, alongside one or two bug reports of the behavior.

Open issues0

No open issues.

Open PRs1

  • PR#20506fix(gateway/config): merge top-level platform keys into extra (#20501)

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #109173 Top-level platform keys like platforms.webhook.port reach the adapter (#10206, #20501)

    merged to main

    files: gateway/config.py, gateway/config_loader.py, tests/gateway/test_config.py, website/docs/user-guide/messaging/webhooks.md

5 PRs closed without merging

From the close comments: duplicate 3 · PR volume cleanup 1 · done elsewhere 1

  • #10211 fix(config): forward unknown platform keys into config.extra · duplicate → #10453
  • #10219 fix(gateway): pass unknown platform config keys to extra · duplicate → #10453
  • #10453 fix(gateway): preserve top-level platform config keys · PR volume cleanup
  • #20528 fix: read top-level api_server config fields into extra · done elsewhere
  • #21114 fix(gateway): honor top-level platform config extras · duplicate → #20506, #10453
Closed issues · 2
  • Closed#10206[Bug]: platforms.webhook.port in config.yaml does not work
  • Closed#20501platforms.api_server config values (port, host, key) silently ignored when not nested under 'extra'
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.26: 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
#109173
Closed issues
2
Attempts
5 PRs closed without merging
Fix link checked
12 Sep 2026

For your agent

The same facts, typed.

cluster/10206.json
cluster/10206.md