From 5df21bb790d59b51666e99c8a1c2858af3f39d81 Mon Sep 17 00:00:00 2001 From: Ogulcan Celik Date: Thu, 4 Jun 2026 01:00:52 +0300 Subject: docs: finalize 0.6.8 release notes --- website/src/content/docs/persistence-remote.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (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 7ffffb7f..3e25dd69 100644 --- a/website/src/content/docs/persistence-remote.mdx +++ b/website/src/content/docs/persistence-remote.mdx @@ -102,7 +102,7 @@ herdr --remote workbox --handoff If you SSH into the server first and run `herdr` there, Herdr runs entirely on the server. That mode is useful and simple, but it cannot access your local desktop clipboard beyond normal terminal text paste. -When your local and remote platforms match, Herdr can copy the current local binary for direct installs. For Homebrew and Nix installs, or when the platforms differ, it downloads the matching release asset for the current client version from `https://herdr.dev/latest.json`. +When your local and remote platforms match, Herdr can copy the current local binary for direct installs. For Homebrew, mise, and Nix installs, or when the platforms differ, it downloads the matching release asset for the current client version from `https://herdr.dev/latest.json`. For local builds or custom binaries, set `HERDR_REMOTE_BINARY` to a local file path before running remote attach. -- cgit v1.2.3