/provider display shows OpenRouter despite custom base_url configured
Cluster 3292 · gateway. Data as of
Nothing open on GitHub. Fix merged in #57002 on 2 Jul 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #57002. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
The three members concern the /provider (status) output labeling OpenRouter even when a custom provider or model.base_url is set in config.yaml. They include a bug report and two fix-oriented pull requests, one described as a salvage of #3296; their outcomes are not stated in the titles.
Open issues0
Open PRs0
Fixes on record
-
#57002 fix(status): provider label honors config.yaml model.base_url (#3296 salvage)
files:
hermes_cli/status.py,scripts/release.py,tests/hermes_cli/test_status_provider_label.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#3296 fix: /provider shows OpenRouter when custom base_url is set in config.yaml · merged via another change →
#57002
Closed issues · 1
- Closed#3292[Bug]: Current /provider incorrectly shows as OpenRouter while custom provider is used
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.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
- gateway
- Merged PRs
- #57002
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 2 Jul 2026