Cairn

providers config URL validation and alias key fixes

NousResearch/hermes-agent · cluster 9332

Data as of

Nothing open on GitHub. Fix merged in #12993. Check it covers your case.

The short answer

0open issues
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #12993. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #12993. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and pull requests address bugs in providers configuration handling, specifically around validating that base URLs are proper URLs and ensuring camelCase alias keys are accepted alongside snake_case variants.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #12993 fix(config): validate providers config entries — reject non-URL base, accept camelCase aliases (#9332)

    merged to main

    files: hermes_cli/config.py, tests/hermes_cli/test_provider_config_validation.py

4 PRs closed without merging

From the close comments: superseded by another PR 3 · merged via another change 1

  • #9359 fix(config): validate providers config entries — reject non-URL base, accept camelCase aliases · merged via another change → #12993
  • #9373 fix(providers): accept camelCase aliases and validate URL scheme in providers: config (#9332) · superseded by another PR → #12993, #9359
  • #9387 Fix providers config alias handling · superseded by another PR → #12993
  • #9507 fix(config): validate provider URLs and accept alias keys · superseded by another PR → #12993
Closed issues · 1
  • Closed#9332[Bug]: providers: config entries silently ignore apiKey/baseUrl and accept non-URL strings as base_url via the api field
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.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

Merged PRs
#12993
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
20 Apr 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.

For your agent

The same facts, typed.

cluster/9332.json
cluster/9332.md