Cairn

Env vars overriding explicit platform disabled config

NousResearch/hermes-agent · cluster 25065 · gateway

Data as of

Nothing open on GitHub. Fix merged in #96557. Check it covers your case.

The short answer

0open issues
0open PRs
9items grouped
Known?
Yes. 9 related items grouped here, 3 issues already closed.
Fix event
A fix was merged to main in PR #96557. 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.

Bug reports and fixes where environment variables (TELEGRAM_BOT_TOKEN, HASS_TOKEN) unconditionally enable gateway platforms, ignoring explicit enabled: false settings in config.yaml.

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.

  • #96557 fix(gateway): WHATSAPP_ENABLED=true no longer overrides an explicit platforms.whatsapp.enabled: false (#73289, salvage #73303)

    merged to main

    files: contributors/emails/[redacted:email], gateway/config_env.py, tests/gateway/test_env_override_explicit_disable.py

5 PRs closed without merging

From the close comments: done elsewhere 3 · superseded by another PR 1 · other 1

  • #25089 fix(gateway): stop HASS_TOKEN from overriding enabled: false · other → f7689f4, #132469
  • #25405 fix(gateway): respect disabled Home Assistant env override · superseded by another PR → #25089, #21676, #25065
  • #35562 fix(gateway): respect explicit platform enabled:false in YAML config · done elsewhere → #35555
  • #36014 fix(gateway): respect disabled telegram config · done elsewhere → #35555
  • #55447 fix: respect config.yaml enabled:false for HomeAssistant/Email/SMS (#55113) · done elsewhere → 867e415, 73a9c34, #96557
Closed issues · 3
  • Closed#25065HASS_TOKEN env unconditionally force-enables Home Assistant gateway platform, overriding config.yaml `platforms.homeassistant.enabled: false`
  • Closed#35555Profile config ignored when TELEGRAM_BOT_TOKEN is in environment
  • Closed#55113[Bug]: Telegram gateway platform force-enabled by TELEGRAM_BOT_TOKEN env, ignores config.yaml platforms.telegram.enabled: false
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.19: 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
#96557
Closed issues
3
Attempts
5 PRs closed without merging
Fix link checked
14 Sep 2026

For your agent

The same facts, typed.

cluster/25065.json
cluster/25065.md