Feature Request: option to relaunch a profile when it exits

[tatroc]

If I have a ssh.exe session open to another machine using ssh.exe (Openssh) and I disconnect from the network the session hangs in the Windows Terminal. I must close the tab. Could we make the session resume by pressing enter? Or is there a better way to handle this?

{
"guid": "{5f77e6d6-8215-45d0-be70-a277c72accf6}",
"hidden": false,
"name": "user@host",
"commandline": "ssh.exe user@host",
"fontFace": "Consolas",
"fontSize": 12,
"icon": "%USERPROFILE%\AppData\Local\lxss\bash.ico"
},

[DHowett-MSFT]

Thanks for the request! I've triaged it and converted it into a request to relaunch a profile when it exits.

[DHowett-MSFT]

For now, you can relaunch a new copy of that profile with ctrl+shift+d (duplicateTab)

[KalleOlaviNiemitalo]

Would relaunching the profile preserve the screen buffer, window title, and WT_SESSION environment variable?

[zadjii-msft]

From #4772: It might be nice if this was an enum value for closeOnExit. Something like "reconnect" to automatically reconnect (or reconnect after prompting for enter or something) to re-spawn the connection.

There's also #3726 for "manually restart a connection", which is similar, but different.

[thernstig]

I wrote a duplicate for this (which I have now closed) that might contain some more context: #10075 But in short, this happens all the time when in hibernation or on bad Wifi, and I want to preserve my screen buffer etc. to continue where I left of.

One solution would be to display some text at the bottom of the buffer similar to how like done here in the April 2021 release of VS Code: https://code.visualstudio.com/updates/v1_56#_untitled-editors-hint. So a Press Enter to relaunch shell might be an option.

But I also do like the closeOnExit: "reconnect" as an added thing for users.

[masics]

We need to reconnect in the same tab.

• It will keep the order of the tabs
• No need to close the original tab manually
• It will keep the screen buffer

[SteffenBlake]

I have created a very simple little powershell script one can utilize to sort of replicate this behavior.

Save the following script to: C:\Windows\System32\Keep-Alive.ps1

$command=$args[0]

while ($TRUE) {
    Invoke-Expression $command
    Start-Sleep -Seconds 1
    Write-Output "Scope ended. Press Enter to reload."
    Read-Host
}

Then you can put your SSH or whatnot call nested within this function call to loop it on exit.

For example I put the following as my command for my profile's Command Line field:

PowerShell Keep-Alive 'ssh rancher@Usagi -i \"C:\Users\MyName\Documents\SSH Keys\Usagi\Usagi.pem\"'

Then you get something like the following:

[swinder0161]

Highly needed feature for the reasons mentioned above.
Comparison: iterm2 for mac has this feature and would be great we have in windows terminal too.

WT is great but can be even better and the greatest terminal emulator out there.

[sisrfeng]

modified from above :

1. create a file called C:\Windows\System32\leo_keep.ps1

$leo_command=$args[0]

while ($TRUE) {
    Invoke-Expression $leo_command
    Start-Sleep -Seconds 1
    Write-Output "leo: ssh disconnected,  Press Enter to reload."
    Read-Host
}

2. use PowerShell leo_keep 'ssh -X you@yourip' instead of 'ssh -X you@yourip at windows terminal' s profile

---

Set-ExecutionPolicy -ExecutionPolicy unrestricted

I think it is not that unsafe to use unrestricted

---

About Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass:

[swinder0161]

In wt profile use: wt_ssh.bat 192.168.1.100

modify ssh %1 to you command. No need of powershell to execute it. No policy change needed.

n followed by enter will terminate and exit
any other key followed by enter or simply press enter to reconnect.

wt_ssh.bat

@echo off

:START
ssh %1

echo.

set /a reconnect=y
set /p reconnect="ssh connection terminated, do you want to reconnect(Y/n)?"
rem echo reconnect: %reconnect%

echo.

if %reconnect%==n (echo exit) else (goto START)

[IBNobody]

In wt profile use: wt_ssh.bat 192.168.1.100

modify ssh %1 to you command. No need of powershell to execute it. No policy change needed.

n followed by enter will terminate and exit any other key followed by enter or simply press enter to reconnect.

wt_ssh.bat

@echo off

:START
ssh %1

echo.

set /a reconnect=y
set /p reconnect="ssh connection terminated, do you want to reconnect(Y/n)?"
rem echo reconnect: %reconnect%

echo.

if %reconnect%==n (echo exit) else (goto START)

Change ssh %1 to ssh %*. Some of us need ssh with extra switches.

[EBADBEEF]

I would also like this feature but if anyone else stumbles here like I did here is my one-liner workaround.

Automatically restart ssh in a loop: cmd /C for /L %i in (0,0,1) do @ssh user@host
Add a sleep in the loop: cmd /C "for /L %i in (0,0,1) do @ssh user@host & timeout /T 2"
Add a command to ssh (for me, reattach tmux): cmd /C "for /L %i in (0,0,1) do @ssh user@host -t . ~/.bashrc; my-tmux-bash-function %COMPUTERNAME% & timeout /T 2"

I couldn't figure out how to use '&' in the ssh command because windows cmd/for will interpret that. There is probably a way to escape it.

[ghost]

🎉This issue was addressed in #14060, which has now been successfully released as Windows Terminal Preview v1.17.1023.:tada:

Handy links:

• Release Notes
• Store Download