From 89d4f3516ca41c06afb7205b62dba0e84781b0d4 Mon Sep 17 00:00:00 2001 From: Ogulcan Celik Date: Fri, 22 May 2026 20:09:24 +0300 Subject: docs: finalize release docs for 0.6.1 --- website/src/content/docs/persistence-remote.mdx | 2 ++ 1 file changed, 2 insertions(+) (limited to 'website/src/content/docs/persistence-remote.mdx') diff --git a/website/src/content/docs/persistence-remote.mdx b/website/src/content/docs/persistence-remote.mdx index 2452fc9a..d6c02f0a 100644 --- a/website/src/content/docs/persistence-remote.mdx +++ b/website/src/content/docs/persistence-remote.mdx @@ -71,6 +71,8 @@ herdr --remote ssh://you@server:2222 In this mode your local Herdr is a thin client. It connects over SSH, starts or attaches to the remote Herdr server, and streams the UI back to your local terminal. Because the client runs locally, Herdr can bridge local desktop features such as image clipboard paste into the remote session by copying the image to a remote temp file and pasting that path. +By default, `herdr --remote` uses your local Herdr keybindings for that attach. This keeps local muscle memory even when the remote server has different config. The local keybindings are a snapshot from attach time; detach and reattach after editing local keybindings. Use `--remote-keybindings server` when you want the remote server config instead. Local custom command keybindings are not sent, because those commands would run on the remote host. + For repeat targets, use your SSH config: ```text -- cgit v1.2.3