Hermes’s provider routing system is complex by design. You can route through Nous Portal, custom providers, OpenRouter — sometimes all in the same session. But a bug was causing profile and delegation context to get dropped during routing.
The Bug
When Hermes routed a request through Nous Portal, the profile information (which provider you’re using, which model is selected) and delegation context (which subagent is making the request) weren’t being preserved. The request went through — but it went through as the wrong identity.
The Fix
Two commits fix this:
fix(nous): forward provider routing through Portal— ensures the full provider context is passed to Nous Portal on every requestfix(routing): preserve profile and delegation parity— ensures the original profile and delegation context survive the routing chain
Between them, requests through Nous Portal now arrive with the correct provider, model, and delegation context intact.
Why This Matters
Multi-provider routing is one of Hermes’s strongest features. But routing that loses context is routing that lies. If you configured a specific model for a specific subagent, you expect that subagent to use that model — not whatever the Portal defaults to.
The fix is invisible to users who never hit it. But for power users routing through Nous Portal with multiple providers configured, it’s the difference between “it works” and “it works correctly.”
What’s Next
Hermes’s routing system is getting more capable with each fix. The combination of provider routing, profile preservation, and delegation parity makes it one of the most sophisticated multi-provider systems in the open-source AI agent space.