# NousResearch/hermes-agent · Persist /sethome home channel to .env rather than config.yaml

## Open now

- 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.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #6447: \[Bug\]: Gateway /sethome command writes channel ID in config.yaml instead of .env file

## Prior & competing PRs

- **#6450: fix(gateway): write home channel to .env instead of config.yaml**. closed without merge · fix tier `suggested`
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `#6447`
- **#6452: fix(discord): persist /sethome home channel to .env**. closed without merge
  - maintainer direction: category `silent_close`; implication `active`

## Fix status

- No merged fix on record.
- Subsystem: `gateway`