You can use screen/tmux, but they’re both more complicated and less good when it comes to this specific use-case.

Personally I use both - mosh (or et) for the seamless automatic-reconnect, and tmux as a console window-manager.

> You can use screen/tmux, but they’re both more complicated...

In what way are they more complicated? Granted screen is legacy, but tmux is just an executable on the server with sane defaults that Just Works OOTB.

> In what way are they more complicated?

When you change wifi networks you either have to remember to manually disconnect in advance, or wait for ssh to time-out the connection, then you have to create a new ssh connection, then you have to run an extra command to re-attach to the {screen/tmux} session you started earlier.

It’s not insurmountably difficult work - but for the specific use-case of roaming across wifi networks, “doing a small disconnect and reconnect dance” with tmux is way more complicated and annoying than “open your laptop and all your connections are still working” with mosh.

What? Instead of ./command you type screen ./command.

Will `screen ./command` automatically and seamlessly reconnect my ssh session when I roam between different wifi networks? Or do I need to reconnect to ssh for myself, and then run a second command to reattach to the screen session?

The second.