Choose Models in Hermes Desktop Without Changing Profile Defaults
Hermes Desktop separates quick chat selection from durable profile configuration. The composer picker is sticky local UI state, a switch inside a live chat is session-scoped, and Settings → Model controls the per-profile default used by new chats and automated work.
Official documentation: Open the official guide
Related model configuration: Open the official guide
Know which setting you are changing
The picker beside the composer microphone lets you select model, reasoning effort, and fast mode. Its choice follows new chats and restarts on that device, but it does not rewrite the profile default. In a live conversation, a change applies to that current chat.
Use Settings → Model when you deliberately want to change the profile's main default. That default is broader: it is the starting point for new chats, cron jobs, subagents, and auxiliary tasks unless they have their own override. Each profile keeps its own default.
Desktop also remembers effort and fast-mode presets per model. Those conveniences are reapplied when you choose that model in Desktop; they do not automatically retune cron jobs or delegated workers.
Decision checklist
- For one current conversation, change the composer picker in that chat.
- For future Desktop chats on this device, confirm the sticky picker state.
- For a durable per-profile default, use Settings → Model.
- Review cron and subagent overrides separately before claiming they changed.
- Confirm provider, cost, privacy, and capability fit before selecting a model.
- On a long chat, consider starting fresh instead of switching models repeatedly.
Common pitfalls
- Assuming the composer picker changes every workload. It never writes the profile default.
- Assuming a profile default rewrites existing sessions. Already-running chats can retain their own state.
- Ignoring prompt-cache cost. A mid-chat model switch resets the prompt cache, so the next turn rereads the conversation at full input price.
- Treating effort presets as global policy. They are Desktop conveniences tied to each model.
Verification
Create a harmless short chat, note its selected model and effort, then open Settings without saving changes. Start a second chat and verify the sticky picker behavior. Finally inspect the profile default and any cron or worker override separately. Report each scope independently rather than saying “the model changed everywhere.”