Hermes Agent updates model lists via hosted JSON for Nous Portal and OpenRouter
Hermes now pulls provider model lists from hosted JSON so new releases appear without client updates. The same update batch also auto-switches to a local browser when an agent needs localhost access.
TL;DR
- According to Teknium's update, Hermes now pulls model lists from a hosted JSON for providers including Nous Portal and OpenRouter, so new model releases can show up without shipping a new Hermes client.
- NousResearch's confirmation framed the change the same way: no more client updates just to pick up new Nous Portal or OpenRouter models.
- In the same update batch, Teknium's localhost browser post says Hermes Agent can detect when a task needs a locally hosted site and switch off a cloud browser backend to a local browser automatically.
Teknium's hosted JSON update points to a PR that moves provider model curation out of the shipped client and into a hosted list, while Teknium's localhost browser post points to a separate PR aimed at a very specific agent failure mode: cloud browsers cannot reach localhost. NousResearch's confirmation makes clear the first provider targets are Nous Portal and OpenRouter.
Hosted JSON model lists
The practical change is small and useful. Hermes no longer needs a release every time Nous Portal or OpenRouter adds a model, because the app now fetches those provider lists dynamically from a hosted JSON instead of relying on a baked-in catalog.
That shifts model curation from client updates to a remote source. Teknium's update says more providers are coming, and NousResearch's confirmation confirms the no-update flow for Nous Portal and OpenRouter specifically.
Local browser switching for localhost
The second change targets web dev workflows. If Hermes Agent is using a cloud browser backend but the task needs to inspect or interact with a locally hosted site, Teknium's post says it now auto-detects that case and switches to a local browser so the agent can actually reach the service.
Teknium says the behavior lands through hermes update, which suggests the browser routing logic ships as a normal client update even as model-list changes move to the hosted path. That makes these two updates complementary: one reduces release churn for provider catalogs, the other fixes localhost access for agent browser sessions.