See What SSH Is Waiting For, Then Retry
A development host waking from sleep should not look like a frozen terminal. Nash 0.13.11 makes the wait visible and keeps a failed connection's error on screen, with a choice to retry when you are ready.
Know Which Stage Is Waiting
The connection window distinguishes the network connection, the SSH server's response and key exchange, and login. When a stage takes at least a second, a live line reports the wait, for example:
Waiting 12s of 30s for the SSH server to answerThe line updates each second. A slow network connection and a server that accepts the connection but takes time to answer no longer look identical. Login still uses the connection window for any prompts it needs.
Give a Sleeping Host More Time
Nash reads ConnectTimeout from the host's entry in ~/.ssh/config. Without an
explicit value, the network connection and SSH handshake each get 30
seconds. This is a limit for each of those stages, not a 30-second budget for
the entire connection or a deadline for answering a login prompt.
For a host that needs longer to wake, merge a setting into its existing entry:
Host devbox
ConnectTimeout 60Waiting longer for one attempt is different from repeatedly starting over. Choose a timeout that suits the host rather than relying on retries to make a short timeout work.
Retry Without Losing the Error
When an explicit connection fails, the same connection window stays open with the error and this prompt:
Press R to try again, or Esc to close.Press R or Enter to try again in that window. Press Escape, or close the window, to give up. Nash does not reconnect on a timer or retry a failed login without your input.
This retry flow applies to explicit mux attachments such as nash connect,
nash start --domain, and nash mux connect. If nash connect or --new-gui
started a separate GUI, choosing Escape also ends that GUI.
Automatic startup attachments remain different: a failure does not leave the application waiting at a retry prompt, so startup can fall back to local panes. If you explicitly name a domain whose automatic attachment already failed, Nash shows that failure and asks before trying again.
See Multiplexer Commands for connection commands and Multiplexer Sessions for the difference between local panes and work that persists on a server.