NousResearch/hermes-agent
Gateway send_message not using home channel from config.yaml
Cluster 43335 · gateway. Data as of
3 open items. Fix attempted, not merged.
The short answer
0open issues
3open PRs
5items grouped
- Known?
- Yes. 5 related items grouped here, 1 issue already closed.
- Fix event
- No fix has been merged to main. 1 PR closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 0 issues and 3 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese issues and pull requests all concern the gateway's send_message tool and how it finds the Telegram home channel, with members describing it as reading only environment variables (e.g. TELEGRAM_HOME_CHANNEL) rather than config.yaml values. Several titles propose bridging or loading config.yaml settings into the environment, but the titles alone do not show whether any change was merged or works.
Open issues0
Open PRs3
1 PR closed without merging
From the close comments: duplicate 1
-
#43489 fix(gateway): bridge config.yaml env vars for send_message tool (#43335) · duplicate →
#43361,#43335,#43362,#43364
Closed issues · 1
- Closed#43335Gateway send_message tool ignores TELEGRAM_HOME_CHANNEL config
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.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- gateway
- Closed issues
- 1
- Attempts
- 1 PR closed without merging