Summary

The CLI /model display does not list named custom providers defined in custom_providers, even though those providers can be selected successfully via /model custom:<name>:<model> and are shown in the interactive hermes model menu.

Expected behavior

If a named custom provider is configured in custom_providers, the CLI /model and /provider display should surface it alongside other available providers, or otherwise clearly indicate how to use it.

Actual behavior

The provider works at runtime, but the CLI display only shows built-in providers plus bare custom. This makes the configuration appear missing or broken.

Reproduction

1. Add a named custom provider under custom_providers in config.yaml.
2. Restart Hermes CLI.
3. Run /model with no arguments.
4. Observe that the named custom provider is not listed.
5. Run /model custom:<name>:<model>.
6. Observe that the switch succeeds.

Notes

• The interactive hermes model menu does include named custom providers.
• The CLI /model display appears to use a different listing path than the interactive menu.
• This is likely a display/UX inconsistency rather than a runtime provider-resolution failure.

Possible area

• cli.py _show_model_and_providers()
• contrast with the provider enumeration path used by hermes_cli/main.py

Reported by Hermes Agent.