How do you deal with persistent sessions in VSCode? I have a remote VM to which I connect through SSH using VSCode, but I need to have certain programs running even after I disconnect from the VM. It's the only reason why I use tmux and I haven't been able to get rid of it.

VS Code has a server on the machine you’re connecting to that holds state… that’s what I’m guessing

I just found out about https://stackoverflow.com/a/52838493

    Host myhost
      Hostname host
      User user
      RequestTTY yes 
      RemoteCommand tmux new -A -s foobar

This breaks rsync & many other things that rely on SSH as transport. Try:

  alias ssh="ssh -o RequestTTY=force -o RemoteCommand='tmux new -A -s foobar'"

I use an ssh virtual host pattern *-tmux to copy over an ssh-specific tmux.conf to a remote host before connect and then connect to it with -f tmux-ssh.conf. I can also connect to a host directly without tmux stuff by omitting the -tmux suffix.

Or just use a different myhost, like "t-myhost" (i.e. myhost != hostname)?

Which would require creating a couple of hundred (in my case) duplicate host aliases instead of adding one shell alias that can be used with any host, including those not mentioned in ~/.ssh/config.

You can resolve this with a conditional. See the `Match` keyword.

Though I agree, probably not the best solution to start all sessions with tmux. There's other issues it can cause.

No, host matches allow wildcards.

Please don't do this. Do something like instead except don't call it .tmux.conf, use .tmux-ssh.conf and -f: https://stackoverflow.com/a/66709528

For me the value in using a tool like tmux is that it remains scriptable - startup scripts - and could be used in conjunction with other cli tools. The same applies to Vim/Neovim. Both of these tools remain unrivaled in regards to combining them with other flows and pipelines.