NousResearch/hermes-agent

Telegram reactions env override ignored by YAML default

Cluster 109032. Data as of 2026-10-24 04:06 UTC

Nothing open on GitHub. Fix merged in #110293 on 13 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #110293. 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.

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

Read #110293 Pick up a Lab task

A regression caused TELEGRAM_REACTIONS environment variable to be silently overridden by the materialized YAML default. These issues and fixes address env → YAML → default resolution order for per-profile adapter settings, particularly for Telegram reactions.

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.

#110293 fix(platforms): per-profile adapter settings resolve env → own YAML → default under multiplex (#108440 review, salvage #109036 #109477 #110109 #110111 #110131)

merged to main

files: gateway/authz_mixin.py, gateway/platforms/_shared.py, gateway/platforms/base.py, gateway/platforms/weixin.py, gateway/platforms/yuanbao.py, gateway/run_topics.py, plugins/platforms/a2a/adapter.py, plugins/platforms/discord/adapter.py, plugins/platforms/feishu/adapter.py, plugins/platforms/matrix/adapter.py, plugins/platforms/slack/adapter.py, plugins/platforms/telegram/adapter.py, plugins/platforms/whatsapp/adapter.py, tests/gateway/test_adapter_settings_scoped_precedence.py, tests/gateway/test_matrix_recovery_key_scope.py, tests/gateway/test_session_title_rename_lane.py, tests/gateway/test_shared_platform_boilerplate.py, tests/gateway/test_slack_thread_require_mention.py, tests/gateway/test_telegram_group_gating.py, tests/gateway/test_telegram_polling_progress.py (+10 more)

2 PRs closed without merging

From the close comments: done elsewhere 1 · duplicate 1

#109036 fix(telegram): let an explicit TELEGRAM_REACTIONS beat the materialized YAML default · done elsewhere → b602ba2, d92490a, 545e74d, ac44aa5, 0f123d5, #110293, #109032
#109090 fix(telegram): honor explicit reactions env override · duplicate → #109036, #109032

Closed issues · 1

Closed#109032bug(telegram): TELEGRAM_REACTIONS=true is silently ignored when config.yaml carries the stock `telegram.reactions: false` (regressed in 545e74d0ea)

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

For your agent

The same facts, typed.

cluster/109032.json
cluster/109032.md