Hermes BibleUnofficial Docs
← All docs Docs / Using Hermes

Configuring Models

Configuring Models Hermes uses two kinds of model slots: Main model — what the agent thinks with. Every user message, every tool call loop, every streamed respo

Using Hermes
Section
Using Hermes
Source
hermesbible.com/docs/user-guide/configuring-models

Configuring Models Hermes uses two kinds of model slots: Main model — what the agent thinks with. Every user message, every tool call loop, every streamed respo

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. The Models page
  2. Setting the main model
  3. Setting auxiliary models
  4. Common override patterns
  5. Per-task override
  6. Reset all to auto
  7. The "Use as" shortcut
  8. What gets written to config.yaml
  9. When does it take effect?
  10. Troubleshooting
  11. "No authenticated providers" in the picker
  12. Main model didn't change in my running chat
  13. Auxiliary override "didn't take effect"
  14. I picked a model but Hermes switched providers on me

Section map

The Models page

Maps the models page to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Setting the main model

Maps setting the main model to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Setting auxiliary models

Maps setting auxiliary models to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Common override patterns

Maps common override patterns to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Per-task override

Maps per-task override to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Reset all to auto

Maps reset all to auto to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

The "Use as" shortcut

Maps the "use as" shortcut to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

What gets written to config.yaml

Maps what gets written to config.yaml to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Using Hermes doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: The Models page, Setting the main model, Setting auxiliary models, Common override patterns, Per-task override. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: configuring, models, kinds, model, slots. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitUsing Hermes documentation

Use when you need orientation for configuring models before applying exact upstream commands.

Verify firstThe Models page

Open the source anchor for The Models page and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Using Hermes, then open the linked source page for exact current syntax.
  2. Start with the source section for The Models page; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for Setting the main model if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

External messages

Keep human review before sending public posts, customer messages, trading instructions, or team notifications.

Model spend

Set provider, token, and retry limits before scaling the workflow beyond a single test run.

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page