Hermes Agent Grok Model 404? Use migrate xai to migrate first

If Hermes Agent suddenly switches to the Grok model and 404, don't rush to reinstall or just change the API key. v0.15.0 added xAI model retirement detection and hermes migrate xai to address the issue of old Grok model names remaining in the configuration after retirement. Many 404s are not because the account has expired, but because the model ID is no longer available.

First, determine whether the model is retired

If the same xAI credential can still be logged in, other models can be used, but only one Grok model reports 404, then the model name is suspected first. The official release mentioned that Hermes detects retired models when Doctor and Chat are launched, and provides migration commands. In this scenario, refreshing tokens or refilling keys usually doesn't solve the problem.

Processing sequence

1. First, run the hermes doctor to see if the xAI model has been retired or needs to be migrated.
2. Run hermes migrate xai to have Hermes migrate the old model configuration to the supported model.
3. Then use hermes model to check the current provider and model, confirming that no longer points to the old ID.
4. If you use hermes proxy or external tools, also check their model names in sync.

The easiest to leak are third-party front-end or scripts. You may have already migrated the main Hermes configuration, but clients like Open WebUI, Aider, Cline, and Continue are still requesting old model names, so it looks like Hermes is still broken.

When will the vouchers be checked?

If all xAI requests fail, continue checking OAuth, XAI_API_KEY, base_url, and the network. Single Model 404 First look up the model name; Check all 401 or 403 documents for authorization; When the connection times out, check the proxy and network. Following this order can help avoid many detours.