Model configuration is one of the easiest places for Hermes operators to create confusion without realizing it. The real problem is understanding that Hermes treats provider, model, scope, and auxiliary roles as separate moving parts.
1. Start with the model selector intentionally
hermes model/model <name>/model <name> --provider <provider>
2. Treat provider and model as a pair
If behavior looks wrong, check whether the model name is right but the provider is wrong.
/model gpt-5.4 --provider openrouter3. Decide whether the change is session-only or persistent
- session-scoped:
/model gpt-5.4 --provider openrouter - persisted/global:
/model gpt-5.4 --provider openrouter --global
4. Know where persistent config lives
Persistent config lives in ~/.hermes/config.yaml.
5. Remember auxiliary model lanes exist
visioncompression
Advanced builds may pin one auxiliary role while leaving another to inherit defaults or use automatic provider behavior.
Practical failure checks
- right model name, wrong provider
- expecting a session change to persist without
--global - forgetting that aliases can hide the underlying provider/model pair
- losing a custom endpoint expectation after a provider switch