{"repo":"NousResearch/hermes-agent","public_id":"99604","display_label":"CLI env fallback to ~/.hermes/.env for secrets","summary":"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.","subsystem":"agent","counts":{"members":3,"open_issues":1,"open_issues_distinct":1,"open_prs":2,"closed_issues":0,"merged_prs":0,"attempt_prs":2},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.6666666666666666},"fix_edges":[],"members":[{"kind":"issue","number":99604,"title":"[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","url":null,"state":"open"},{"kind":"pr","number":99616,"title":"fix(cli): fall back to ~/.hermes/.env in runtime provider key resolution","url":null,"state":"open","close_reason":{"refs":[{"kind":"commit","value":"a7caf0ddb6","number":0}],"category":"implemented_elsewhere","implication":"superseded"},"merged":false},{"kind":"pr","number":128781,"title":"fix(cli): fall back to ~/.hermes/.env in runtime provider key resolution","url":null,"state":"open","close_reason":{"refs":[{"kind":"pr","value":"#99604","number":99604}],"category":"uncategorized","implication":"needs_llm"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}