This should be mostly fixed by #7201, please let us know if it's still a problem after the next version of Coder is released (next after v0.22.2).

(Although we may still want to implement the SSH termination sequence, ↩~., used by OpenSSH.)

I'll give the new version a try. One of my biggest needs for this is the connection gets stuck in a "hanging" state when using --forward-gpg and my laptop goes to sleep (for example lid closed). Not sure if the PR linked handles that scenario too, but will report back if the problem continues.

This is definitely still an issue that plagues me regularly. It can happen due to network connectivity issues, issues with gpg agent, laptop going to sleep, etc. Honestly having ↩~. would be a godsend.

Thanks for reporting back @julianpoy. Just to confirm, this is happening with the coder ssh command?

Ultimately we probably need to resolve something in the network stack so that connections can be re-established in more scenarios. For now, I'm re-opening this to track the addition of ↩~. to coder ssh.

Yep, it's with the coder ssh command.

Improving the resiliency of the network stack would be excellent too, but just having an escape sequence would solve so much. Avoids me having to kill my terminal and open a new one.

Thank you and the team for all you do!

Any update on this, I've experienced this as well