Cairn
NousResearch/hermes-agent

CLI env fallback to ~/.hermes/.env for secrets

Cluster 99604 · agent. 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.

A feature request and related fixes address secret resolution failures when running in Desktop-SSH headless mode, where provider keys, MCP tokens, and other env-backed secrets are read via raw process environment instead of the .env-aware helpers. The fix adds a fallback to ~/.hermes/.env during runtime provider key resolution.

Open issues1

  • Issue#99604[Feature]: Desktop-SSH headless backend can't see secrets: secret readers use raw `os.getenv` / `${VAR}` (process env only) instead of the `.env`-aware helpers — provider keys, MCP tokens, and every other env-backed secret fail in Desktop SSH mode

Open PRs2

  • PR#99616fix(cli): fall back to ~/.hermes/.env in runtime provider key resolution
  • PR#128781fix(cli): fall back to ~/.hermes/.env in runtime provider key resolution
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
agent
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/99604.json
cluster/99604.md