How Do You Verify a Hermes Agent Uninstall?

Use your OS package inventory, process viewer, and service manager to identify the Hermes install you own. Record which components should disappear and which data should stay readable, then check both after signing in again.

Match the uninstall route to package ownership

Start with the installed application record, the executable path of any running Hermes process, and the launch registration that starts it. The official installation guide distinguishes a Windows MSIX package installed through App Installer, separate Microsoft Store ownership, a macOS app copied into Applications, and a bootstrap installer that builds from source. Use the OS package owner for a registered installation. For an app bundle, verify which copy the process actually runs before retiring that copy. For a bootstrap installation, locate the source checkout and identify any service or launcher pointing to it before selecting the removal route. If an app launcher disappears but a process still runs from a checkout, record both as separate components. Repeat the process check after sign-in to catch a launch registration that survived the first check.

Install Hermes Agent: Official Guide | Nous Research

Prove the retained skills still open

Hermes documents that bundled, hub-installed, and agent-created skills share the local skills directory. It can also scan external skill directories. Inventory the local and external roots independently and decide which copies to retain while the install is still intact. For each retained root, pick a representative skill document and any companion file the workflow needs. Read them under the intended account, then record a comparison fingerprint or an expected excerpt from a nonsensitive fixture. After removal, repeat the checks from the retained location. A folder that still appears in a file browser can contain unreadable files or a link to a checkout that is gone. Record unreadable or mismatched contents as a failed retention check. If an external directory is shared with another application, verify it from that application’s usual account as well.

Skills System | Hermes Agent

Identify the installation you own

Start with the installer that put Hermes on the machine. The official guide distinguishes the packaged Windows MSIX and macOS application from the Hermes-Setup bootstrap installer, which downloads a source installation. On Windows, the guide also distinguishes Microsoft Store ownership. Record where you launch Hermes and which installation method owns that copy before choosing a removal procedure.

Use the operating system’s app removal controls for a registered desktop package. For a source installation, stop any Hermes background process through its service controls, then confirm the removal command and its data options in the installed version’s help or matching official instructions. If a launcher still resolves afterward, inspect its target. A surviving launcher can point to another installation.

Install Hermes Agent: Official Guide | Nous Research

Decide whether custom skills survive

If you’re removing Hermes to troubleshoot a bad install, keep a readable copy of the custom skills you would want on a replacement. Check the main skills directory and review the configuration for external skill folders. Record the original paths alongside the backup so you can tell which files came from Hermes’ main directory and which belong to a separate project.

In an illustrative reinstall, suppose you have two custom skills under ~/.hermes/skills/ and a third in a shared project directory. Copy the first two to a protected location and verify that you can open both copies. Record the third skill’s path and leave its shared folder in place. After reinstalling, restore and test one custom skill at a time so you can identify which restoration brings back the original problem.

Skills System | Hermes Agent

Inspect the Docker data mount

If Hermes runs inside Docker, inspect the container’s mounts and record the host source mapped to /opt/data before removing the container. The documented setup puts configuration, API keys, sessions, skills, and memories in that mount. Leaving the mount available preserves the option to restore the installation. A wipe requires a separate decision about the backing storage.

Use the container manager to stop and remove the intended Hermes container, then confirm that it is gone. Check the recorded host source separately. For a rollback, verify that the expected files remain readable. For a wipe, confirm the storage belongs exclusively to the retired instance before deleting it, then verify that the recorded source is gone. Inspect the mount again if the name or path differs from what you recorded.

Hermes Docker Setup | Hermes Agent

Check the endpoint after sign-in

If you enabled the Hermes API server, record the endpoint your client uses before removal. Hermes documents that endpoint as OpenAI-compatible, so a saved frontend entry can look much like one for a different backend. Once you’ve stopped and removed the local runtime, check the recorded endpoint again, then repeat the check after signing back in if the installation had an automatic startup entry.

If the old address still responds, verify which process owns the listening port and whether the client is using that exact address. Trace a local listener back to its app, service, or container before removing anything else. If the listener is gone but the old backend still appears in the frontend, remove the stale connection entry from the frontend’s settings.

API Server | Hermes Agent

Sources