CONFIGURATION RELIABILITY
Hermes Model Picker Provider Grouping Error #66329
A documented P2 configuration issue in which the selected model can appear under a generic custom-endpoint group rather than its configured named provider, complicating provider selection and review.
Documented behavior
The model picker reportedly displays a selected model under “CUSTOM ENDPOINT” instead of the configured named provider. The concern is not merely cosmetic: ambiguous grouping can lead a reviewer or operator to believe that a model is attached to the wrong provider configuration.
Evidence boundary: This page summarizes a reported issue and a cautious reproduction protocol. It does not establish that every configuration or installation is affected.
Verification matrix
| Check | What to inspect | Bounded response |
|---|---|---|
| Provider identity | Does the picker display the configured provider name alongside the chosen model? | Record the intended provider and model before saving, then compare it with the post-save grouping. |
| Endpoint provenance | Is a generic endpoint label masking a named provider configuration? | Inspect the configured base URL, credentials scope, and provider entry rather than inferring from the picker label. |
| Selection persistence | Does the same model remain grouped correctly after restart or configuration edit? | Retest after a restart and preserve screenshots or logs if the group changes. |
| Safe recovery | Can the user distinguish a display defect from an actual provider misconfiguration? | Verify a non-sensitive test request, then correct configuration only with a clear before-and-after record. |
Reproduction and recovery protocol
- Capture the configured provider name, model identifier, and endpoint fields before changing anything.
- Select the model and note the exact group displayed in the picker.
- Restart or reopen the configuration view and repeat the observation.
- Validate the active configuration with a bounded non-sensitive request rather than relying solely on the visual group.
- If the mismatch persists, attach reproducible steps and redacted configuration context to the issue.
Source evidence
GitHub issue #66329 · P2 · Opened July 17, 2026
Issue status and scope can change. Review the linked record before relying on this page for a production decision.