Nous Research announces model and profile routing for Hermes Agent

Choosing a route

Under Model routes, each task can pick a named model route from a user-defined list. Under Profile routes, a task can instead use one of the user's Hermes profiles, including that profile's model, credentials, skills and SOUL.md instructions.

Only one of Default, Model routes or Profile routes can be active at a time. If a task picks no route, it uses the mode's configured default or, if none is set, the parent agent's model. The two added modes keep separate configurations when a user switches between them.

Installing and switching

The documentation specifies Hermes 0.22.5 or newer and gives hermes plugins install advanced-delegation as the catalog installation command. Installation is per profile: the profile delegating tasks needs the plugin, but target profiles do not.

Route changes normally apply to new sessions. The /delegation command's --now option can rebuild the current chat's tools at the next message, but the documentation says that depends on Hermes supporting a running-chat tool rebuild.

Nous Research warns that listing a profile lets subagents use its credentials and terminal policy. For model routes, it recommends provider-based credentials rather than a route-level api_key, which it says is stored as plain text in config.yaml.