NousResearch/hermes-agent

Discord allowed_channels config.yaml setting not being read

Cluster 32263 · gateway. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These members all concern the Discord integration reading channel filtering settings (allowed_channels, and in one case ignored_channels) from config.yaml rather than only from the DISCORD_ALLOWED_CHANNELS environment variable. One title reports the config field as non-functional, and two titles describe fixes aimed at honoring it.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

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

  • #32289 fix(discord): read allowed_channels/ignored_channels from config.yaml · done elsewhere → cc8e5ec, #16078
  • #32307 fix: honor discord.allowed_channels from config.yaml when env var unset · superseded by another PR → #32289
Closed issues · 1
  • Closed#32263discord.allowed_channels config.yaml field is non-functional — only DISCORD_ALLOWED_CHANNELS env var is read
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.67: 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
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.