A reference guide explains the different ways to leave a Herdr session - detaching (ctrl+b then q) keeps the server and all running processes alive, while closing a pane, tab, or workspace ends the processes inside it, and stopping or deleting a session is more destructive. It covers reattaching, remote SSH workflows, direct terminal attach, and what survives a server restart versus what does not.
Table of contents
The quick answerDetach without stopping the workWhat if I close the terminal window?Exit one shellClose a pane from the CLIClose a tabClose a workspaceStop the default Herdr sessionStop and delete a named sessionDetach from a remote sessionDetach from direct terminal attachDetach does not survive every kind of failureI pressed the wrong keysThe rule to rememberQuestions this post answers
How do I detach from a Herdr session without stopping the processes running inside it?
Press ctrl+b, release the keys, then press q. This closes the client connection but leaves the Herdr server, panes, coding agents, tests, and development servers running in the background. Reattach later by running herdr, which returns you to the exact live panes you left. Developers juggling long-running agent sessions can find workflow guides like this through daily.dev.
What is the difference between stopping and deleting a named Herdr session?
Stopping a named session with herdr session stop NAME ends the live runtime and exits the pane processes, but keeps the saved session state so it can be reattached later with herdr session attach. Deleting it with herdr session delete NAME removes that saved state entirely from the session list, discarding it for good. daily.dev surfaces practical breakdowns like this for developers managing multiple terminal sessions.
Does a running coding agent survive a Herdr server restart?
Screen history restores what was visible on screen, not the actual process that produced it, so a coding agent does not automatically survive a full server stop. Normal panes return as new shells after herdr restores the saved layout, but supported coding agents can only resume their own conversations if an official Herdr integration previously recorded their native session IDs. Anyone relying on coding agents in persistent sessions can track these nuances via daily.dev.