Cairn
NousResearch/hermes-agent

Handling ${env:VAR} config refs from Hermes .env files

Cluster 89199 · hermes cli. Data as of

3 open items. Fix attempted, not merged.

The short answer

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

These items concern ${env:VAR} references in Hermes config not being looked up against values in ~/.hermes/.env (or a profile .env), with one report describing a spurious "Config ref ... is not set" warning. Two are fix-oriented changes and one is a bug report, all appearing to address the same theme.

Open issues1

  • Issue#89199[Bug]: hermes config logs spurious "Config ref ${env:VAR} is not set" warning for vars present in ~/.hermes/.env

Open PRs2

  • PR#89218fix(config): resolve ${env:VAR} refs from ~/.hermes/.env
  • PR#142376fix(config): resolve ${env:VAR} refs against profile .env outside secret scopes
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
hermes cli
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/89199.json
cluster/89199.md