Herdr, a persistent terminal session manager, can be accessed from a phone over SSH without a dedicated mobile app or browser dashboard. The guide walks through installing Herdr on a remote machine, configuring SSH keys for secure phone access, using the narrow-screen interface to check on running coding agents, and understanding what survives a dropped connection versus a full server restart. It also covers detaching properly, a security checklist for exposing SSH from a phone, and troubleshooting tips for common connection and keyboard issues.
Table of contents
What you needPrepare the remote machineConfigure SSH keysConnect and open HerdrUse an SSH config nameNavigating on a small screenA practical mobile workflowNormal SSH or herdr —remote?What happens if the connection drops?Detach when you are doneSecurity checklistTroubleshootingMy recommendationQuestions this post answers
How do I check on a coding agent running in Herdr from my phone without a Herdr mobile app?
Install an SSH client on the phone, connect to the remote machine with `ssh you@server`, then run `herdr` to attach to the existing session. Herdr adapts its interface to a narrow terminal, letting you switch workspaces, check which agent is blocked or done, focus a pane, and detach again with ctrl+b then q, without needing a browser dashboard. Developers wiring up remote agent workflows often track tooling changes like this via daily.dev.
What happens to my Herdr session if my phone loses SSH connection while a coding agent is running?
The Herdr server and its pane processes keep running independently of the SSH client, so a dropped connection, network switch, or closed SSH app does not kill the session. Reconnecting with `ssh workbox` then `herdr` returns you to the live terminals. Persistence only breaks if the Herdr server or remote machine itself restarts or reboots. Anyone relying on persistent remote dev sessions can follow workflow tips like this on daily.dev.
What is the difference between detaching from Herdr and running herdr server stop?
Detaching with ctrl+b then q closes the Herdr client but leaves the session and its pane processes running in the background, while `herdr server stop` actually stops the session and exits all its pane processes, ending any running agents or dev servers. Use detach for normal workflow interruptions and reserve the stop command for when you intend to end the work entirely. Teams standardizing remote agent session hygiene can find practical guides like this on daily.dev.