GitHub Repo
Hermes Agent Update Blocked During Repair; Conflicting Plugins Are Disabled With Reasons Logged
The fix handles Python upgrades and dependency conflicts across profiles, preventing a single plugin from blocking core updates. The change has been merged into the main branch, but download failures can also trigger plugin deactivation, so deployments should verify plugin functionality.
On September 25, Hermes Agent merged a fix to its update process that removes incompatible plugins from dependency builds, preventing the entire agent from getting stuck during an upgrade. The triggering case involved a third-party plugin that required a Python version below 3.14 while the new managed interpreter had been upgraded to 3.14. Previously, after the code switch completed, the environment could not be rebuilt, and repeated retries continued to fail. [Merge record](https://github.com/NousResearch/hermes-agent/pull/122103)
The problem is related to the shared dependency architecture. Hermes’s package manager resolves requirements for the core, enabled features, and plugins together; multiple profiles sharing the same installation also contribute dependencies. The official documentation says a new environment must be prepared and validated before switching over, and running processes may still need to be restarted. Plugin compatibility therefore directly affects whether the agent can obtain a usable environment. [Package management documentation](https://hermes-agent.nousresearch.com/docs/reference/package-management)
The fix first checks the Python and plugin manifest versions. If the build still fails, it builds the core on its own, then adds plugins back one by one in configuration order, disabling any that cause a resolution conflict or build failure. It still reports an error if the core itself cannot be built. This also means that when two plugins conflict with each other, configuration order affects which one is kept. Regular plugin enablement and dependency synchronization continue to reject conflicts. [Fix details](https://github.com/NousResearch/hermes-agent/pull/122103)
Deactivation applies across all profiles where the plugin is enabled; if it provides a memory service, the related provider configuration is also cleared. Download or network failures are retried once; another failure may also result in deactivation. By contrast, plugins excluded solely because their Hermes version range does not match retain their configuration and can be added back when the version condition is met. These actions are recorded in the update log, and disabled plugins must be re-enabled and checked for compatibility. [Update documentation](https://hermes-agent.nousresearch.com/docs/getting-started/updating)
For operators, this trade-off reduces the chance that a single plugin will block an update, but they should still confirm after updating that tools and memory features are intact. Start by checking the `hermes pm status` log, then verify tasks that rely on plugins. The package manager itself does not provide a sandbox for plugin code. [Diagnostics and limitations](https://hermes-agent.nousresearch.com/docs/reference/package-management)
At the time of review, the fix had reached the main branch, while the latest release on the public releases page was still v0.21.5, dated September 24. Source installations tracking the main branch and stable releases or desktop packages may receive the change at different times, so verify the actual commit version before deployment. [Release history](https://github.com/NousResearch/hermes-agent/releases), [update channels](https://hermes-agent.nousresearch.com/docs/getting-started/updating)