NousResearch/hermes-agent
base_url_env_var lookup via get_env_value
Cluster 18757 · hermes cli. Data as of
3 open items. Fix attempted, not merged.
The short answer
1open issue
2open PRs
6items grouped
- Known?
- Yes. 6 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 3 PRs closed without merging; 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.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese items address a bug where base_url_env_var was looked up using os.getenv instead of get_env_value, causing values defined in ~/.hermes/.env to be overlooked. Multiple corrections apply get_env_value consistently across auth and CLI code paths.
Open issues1
- Issue#18757[Bug]: resolve_api_key_provider_credentials() uses os.getenv for base_url_env_var — misses ~/.hermes/.env values
Open PRs2
3 PRs closed without merging
From the close comments: superseded by another PR 3
-
#18797 fix(auth): use get_env_value for base_url_env_var instead of os.getenv (#18757) · superseded by another PR →
#23352 -
#18908 fix: use get_env_value() for base_url_env_var resolution · superseded by another PR →
#18797,#18757 -
#18948 fix(auth): resolve base_url_env_var via get_env_value everywhere (closes #18757) · superseded by another PR →
#18797,#18908,#17246
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.33: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- hermes cli
- Closed issues
- 0
- Attempts
- 3 PRs closed without merging