hermes - 💡(How to fix) Fix Automatic background skill patching disrupts active sessions (severe impact on local models)

Describe the bug During an active session, if Hermes learns and fixes new pitfalls, it automatically initiates a background process to patch its custom skills. This forces the model to clear cached prompts, reprocess the new prompts (from its own skills), and perform the patch. Because this happens mid-session, it completely locks up the workflow—especially for local models, which can take several minutes to complete the reprocessing before the user can interact with the session again.

Steps to reproduce Run Hermes using a local model.

• Start an active user session.
• Trigger a scenario where Hermes learns and fixes a new pitfall.
• Hermes automatically begins patching its custom skills in the background.
• The model clears the prompt cache from the current session and begins reprocessing.
• The active session is blocked/unusable until this process finishes.

Expected behavior Background activities like skill patching and prompt reprocessing should not occur while the user is actively working in a session. These maintenance tasks should be deferred until the session is explicitly closed, or they should only execute during extended idle periods.

Actual behavior Hermes initiates the patching process immediately mid-session. For users running local models, this results in a wait time of several minutes while the background process hogs the model's resources.

Workarounds attempted (Failed)

• Killing the process: There is currently no visible way to kill or pause this background task, as it is decoupled from the current session.
• Unloading the model: If I unload the model to regain control, Hermes immediately resumes the patching process as soon as the model is loaded again.

Environment / Impact Setup: Local model Impact: High. This is a significant workflow blocker and creates a highly disruptive user experience.