Cairn
NousResearch/hermes-agent

Add api_key_file support to config schema

Cluster 18709 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue 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 1 PR.

The config schema did not recognize api_key_file fields or related env vars, causing them to be silently ignored. A fix was proposed to properly support API key file references in configuration.

Open issues1

  • Issue#18709[Feature]: Setup templates reference api_key_file: / *_API_KEY_FILE env vars but config schema doesn't recognize them — silently ignored, leading to "I rotated the key" confusion

Open PRs1

  • PR#19252fix(config): support api key files
Closed issues · 1
  • Closed#19203[Feature]: Setup templates / wizard reference api_key_file: (and *_API_KEY_FILE env vars) but config schema doesn't recognize them — silently ignored, leading to "I rotated the key" confusion
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.45: 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
1
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/18709.json
cluster/18709.md