From 6bd8bb6bf197ea3dce470b547ce7b16b8d4450b1 Mon Sep 17 00:00:00 2001 From: Ogulcan Celik Date: Wed, 20 May 2026 04:35:57 +0300 Subject: docs: clarify remote workflows and agent overview --- website/src/content/docs/how-to-work.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'website/src/content/docs/how-to-work.mdx') diff --git a/website/src/content/docs/how-to-work.mdx b/website/src/content/docs/how-to-work.mdx index cd37969b..d127a5f9 100644 --- a/website/src/content/docs/how-to-work.mdx +++ b/website/src/content/docs/how-to-work.mdx @@ -79,7 +79,7 @@ herdr --remote ssh://you@server:2222 Your local Herdr acts as a thin client. It connects over SSH, starts or attaches to the remote Herdr server, and streams the UI back to your local terminal. -Use this path when you want one local command that opens the remote Herdr session directly. +Use this path when you want the remote session to feel local. The client runs on your machine, so local desktop features such as image clipboard paste can be bridged to the remote server. If you SSH first and run `herdr` on the server, Herdr runs entirely on that server and cannot read your local desktop clipboard. For repeat targets, put the host in your SSH config: @@ -98,6 +98,6 @@ herdr --remote workbox ## Which path to use -Use `herdr` for local work. Use `ssh you@server` then `herdr` when you want Herdr to behave like tmux on that remote shell. Use `herdr --remote ` when you want your local terminal to attach directly to the remote Herdr session over SSH. +Use `herdr` for local work. Use `ssh you@server` then `herdr` when you want Herdr to behave like tmux on that remote shell or when you are using a phone SSH client. Use `herdr --remote ` when you want a local thin client for a remote session, including local clipboard image paste bridging. For remote bootstrap details, named remote sessions, custom binaries, direct terminal attach, and `--no-session`, see [Persistence and remote access](/docs/persistence-remote/). -- cgit v1.2.3