Thin-client workflow
Run the multiplexer, agents, and work on a remote box; the laptop is just a window onto it. herder's --remote user@ip makes it one command: SSH in, auto-install if missing, apply your local config and theme. Close the lid and agents keep working — "finally be a responsible father again" (typecraft). Same motivation as dhh's Tailscale + KVM closet fleet, minus the hardware. Prereq: session persistence as a server process.
Technical why (alejandro-ao): running the multiplexer inside SSH streams the whole UI back with latency; --remote keeps the interface local while every process runs on the VPS (report).