Cairn
NousResearch/hermes-agent

Config precedence between .env and config.yaml, Discord settings

Cluster 13685 · gateway. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues 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
1 issue and 1 PR.

The members concern the precedence between environment variables and config.yaml, where documentation says env should win. One is a bug report about config.yaml overriding .env, and two are Discord-specific pull requests about DISCORD_FREE_RESPONSE_CHANNELS and require_mention/free_response_channels.

Open issues1

  • Issue#13685[Bug]: config.yaml settings override .env settings, despite doc says the opposite

Open PRs1

  • PR#89451fix(discord): explicit DISCORD_FREE_RESPONSE_CHANNELS beats config.yaml

1 PR closed without merging

From the close comments: other 1

  • #13732 fix(discord): honor documented env-wins-over-config precedence for require_mention/free_response_channels · other
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
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/13685.json
cluster/13685.md