From c7e469be133fdc6214787cf930fd9718c81008e2 Mon Sep 17 00:00:00 2001
From: teknium1 <127238744+teknium1@users.noreply.github.com>
Date: Wed, 16 Sep 2026 09:57:58 -0700
Subject: [PATCH] docs(desktop): document the SSH Hermes path field in the
 connections editor

The Add/Edit connection editor now exposes the remote hermes executable
path for SSH entries; the multi-connection guide listed only the SSH host
field, so users following the docs could not find the setting the probe
error text points them to.
---
 website/docs/user-guide/multi-connection-desktop.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/website/docs/user-guide/multi-connection-desktop.md b/website/docs/user-guide/multi-connection-desktop.md
index b0d3aeb8ed..644d2b0cfb 100644
--- a/website/docs/user-guide/multi-connection-desktop.md
+++ b/website/docs/user-guide/multi-connection-desktop.md
@@ -134,6 +134,12 @@ authentication; manage sign-in from the registered connection controls.
        shell; on a `zsh` login shell the probe watchdog cannot kill the whole
        process group, so a hung probe's grandchildren may linger on the remote
        (bash/sh remotes reap them).
+     - **Hermes path (optional)** — full path to the `hermes` executable on
+       the remote (for example `/opt/hermes/bin/hermes`). Leave blank to
+       auto-detect. Set it when the remote's non-interactive shell does not
+       have `hermes` on its `PATH` and **Test** reports *"Hermes is not
+       installed on the remote host"*; clearing the field restores
+       auto-detection.
 5. Click **Save connection** (or **Cancel**).
 6. Click **Test** on the new row and wait for *"Reachable"*.