Configuring Models
Configuring Models
Start with meaning, then move to detail.
This lesson explains Configuring Models as part of extending Hermes and connecting external tools. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect The Models page, Setting the main model, Mid-session switches and context warnings, then verify failure modes and version compatibility.
Complete installation and one successful task before adding new capabilities.
A clear outcome before you read.
- Understand Configuring Models without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Provider
- The service that runs or provides access and authentication to a model.
- Session & memory
- A session holds conversation context, while memory keeps selected facts that should persist.
What does the source say, and in what order?
- 01The Models page
Start here to understand the core idea or structure.
- 02Setting the main model
Read this after the foundation, then connect it to the previous step.
- 03Mid-session switches and context warnings
Read this after the foundation, then connect it to the previous step.
- 04Setting auxiliary models
Read this after the foundation, then connect it to the previous step.
- 05Common override patterns
Read this after the foundation, then connect it to the previous step.
- 06Per-task override
Read this after the foundation, then connect it to the previous step.
- 07Reset all to auto
Read this after the foundation, then connect it to the previous step.
- 08The "Use as" shortcut
Read this after the foundation, then connect it to the previous step.
- 09What gets written to config.yaml
Read this after the foundation, then connect it to the previous step.
- 10Per-provider request options
Finish here to verify the result and special cases.
Copy only after you understand the effect.
model:
provider: openrouter
default: anthropic/claude-opus-4.7
base_url: '' # cleared on provider switch
api_mode: chat_completionsauxiliary:
vision:
provider: openrouter
model: google/gemini-2.5-flash
base_url: ''
api_key: ''
timeout: 120
extra_body: {}
download_timeout: 30auxiliary:
compression:
provider: auto
model: ''
base_url: ''
# ... other fields unchangedRead the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.