HermesWatcher
Search⌘K For brandsSetup help
StartStart hereSetup plannerInstall Hermes AgentChat from your phoneYour first 24 hours
Use casesWorkflow blueprintsCase studiesUse-case collectionsCommunity libraryPrompt library
LearnWhat is Hermes Agent?Guideswitcheer's WingtipsTopicsFAQCommand cheat sheetGlossarySOUL.md gallery
ToolsTools & integrationsAll messaging platformsSkills directoryPlugins directorySkills, plugins & MCP
TroubleshootReleases
Work with usServicesNewsletterFor brands: partner with usFor AI agentsContactAboutFollow @HermesWatcher on X ↗ (opens in a new tab)

witcheer's Wingtips #10: every fallback entry needs both provider and model

Republished in his own words, with credit.

witcheerBy witcheer · Nous Research

Back to wingtips

#10 · every fallback entry needs both provider and model

· Models, providers & cost · CLI / Desktop / Gateway

Hermes Wingtips #10: every fallback entry needs both provider and model

your fallback_providers list in ~/.hermes/config.yaml counts an entry as a real fallback only when it carries a provider field and a model field.

two things worth setting:

(1) write provider and model on every entry in the chain, top to bottom.

(2) put a local model last as your floor for a cloud outage, pointing provider: custom at your own llama.cpp or vLLM endpoint.

SourcesHermes docs: Fallback Providers

All tips are written by witcheer and collected here with credit. Card images stay on his X posts.

witcheer says each tip ran on a real Hermes box before it shipped. Hermes changes fast, so check your version and the linked doc.