Cairn
NousResearch/hermes-agent

Persist /sethome home channel to .env rather than config.yaml

Cluster 6447 · 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.

All three members concern the gateway /sethome command (including its Discord handling) and where the home channel ID is stored. One reports it being written to config.yaml instead of .env, and the other two are fixes proposing to write it to .env.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: closed without comment 1 · other 1

  • #6450 fix(gateway): write home channel to .env instead of config.yaml · other → #6447
  • #6452 fix(discord): persist /sethome home channel to .env · closed without comment
Closed issues · 1
  • Closed#6447[Bug]: Gateway /sethome command writes channel ID in config.yaml instead of .env file
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.

cluster/6447.json
cluster/6447.md