New action Restart this tab in the tab&#39;s topbar context menu #23246

@DHowett commented on GitHub (May 10, 2025):

We should probably put it in the menu.

For now, you can get at it with the command palette under the name "restart connection".

@DHowett commented on GitHub (May 10, 2025): We should probably put it in the menu. For now, you can get at it with the command palette under the name "restart connection".

claunia commented

@vadimkantorov commented on GitHub (May 11, 2025):

For Duplicate tab - also please consider creating the new tab right next to the old one (similar to Chrome) and not flushed to the right

And the other idea - is to be able to send some Linux signals (equivalent to Ctrl+C and Ctrl+Z) also directly from the context menu...

@vadimkantorov commented on GitHub (May 11, 2025): For `Duplicate tab` - also please consider creating the new tab right next to the old one (similar to Chrome) and not flushed to the right And the other idea - is to be able to send some Linux signals (equivalent to Ctrl+C and Ctrl+Z) also directly from the context menu...

claunia commented

@jamespack commented on GitHub (May 26, 2025):

It looks like there is already code there for it here

@jamespack commented on GitHub (May 26, 2025): It looks like there is already code there for it [here](https://github.com/microsoft/terminal/blob/main/src/cascadia/TerminalApp/TerminalTab.cpp#L1499-L1518)

claunia commented

@jamespack commented on GitHub (May 26, 2025):

Yea unless Im reading this wrong, this functionality already exists. If the current tab's connection IsClosed() it sets that menu Items Visibility to Visibile. Otherwise its Collapsed. Maybe there is a bug?

@jamespack commented on GitHub (May 26, 2025): Yea unless Im reading this wrong, this functionality already exists. If the current tab's connection IsClosed() it sets that menu Items Visibility to Visibile. Otherwise its Collapsed. Maybe there is a bug?

claunia commented

@jamespack commented on GitHub (May 26, 2025):

@jamespack commented on GitHub (May 26, 2025): ![Image](https://github.com/user-attachments/assets/13ddc440-947c-42d2-8757-fb7570ab3ff7)

claunia commented

@jamespack commented on GitHub (May 26, 2025):

Seems to work

@jamespack commented on GitHub (May 26, 2025): Seems to work ![Image](https://github.com/user-attachments/assets/47502abb-878a-484b-82de-3f76166ac151)

claunia commented

@vadimkantorov commented on GitHub (May 26, 2025):

I'm proposing to always make this menu item available. My usecase is that some program (like ssh) hangs the tab completely, and I'd like to be able forcibly restart the tab (basically kill the existing tab, and create a new tab with the same profile at the same place in the tab bar) - even if the Terminal does not detect the tab as "restartable"

"Restart connection" is also a super strange naming for this...

@vadimkantorov commented on GitHub (May 26, 2025): I'm proposing to always make this menu item available. My usecase is that some program (like ssh) hangs the tab completely, and I'd like to be able forcibly restart the tab (basically kill the existing tab, and create a new tab with the same profile at the same place in the tab bar) - even if the Terminal does not detect the tab as "restartable" "Restart connection" is also a super strange naming for this...

claunia commented

2026-01-31 08:36:36 +00:00

@jamespack commented on GitHub (May 28, 2025):

@DHowett Whats your view on this?

@jamespack commented on GitHub (May 28, 2025): @DHowett Whats your view on this?

claunia commented

@DHowett commented on GitHub (May 28, 2025):

Please do feel free to add it to the menu. However: it is a destructive action; should we guard it as such?

@DHowett commented on GitHub (May 28, 2025): Please do feel free to add it to the menu. However: it is a destructive action; should we guard it as such?

claunia commented

2026-01-31 08:36:36 +00:00

@jamespack commented on GitHub (May 29, 2025):

Yea I feel like this is a different use case. This is a process that is hung either on the remote session or possibly on the client side. It could be tricky to know which. Further, it could become a slippery slope to start killing processes. Id be hesitant to add a menu item that whose intention was to kill processes that we couldnt be 100% sure we knew was the culprit for the hung tab. Thats just my two pennies worth.

@jamespack commented on GitHub (May 29, 2025): Yea I feel like this is a different use case. This is a process that is hung either on the remote session or possibly on the client side. It could be tricky to know which. Further, it could become a slippery slope to start killing processes. Id be hesitant to add a menu item that whose intention was to kill processes that we couldnt be 100% sure we knew was the culprit for the hung tab. Thats just my two pennies worth.

claunia commented

2026-01-31 08:36:36 +00:00

@jamespack commented on GitHub (May 29, 2025):

I suppose at the end of the day if we know what process is responsible for the tab we can restart that process as the tab is useless at that point anyway.

@jamespack commented on GitHub (May 29, 2025): I suppose at the end of the day if we know what process is responsible for the tab we can restart that process as the tab is useless at that point anyway.

claunia commented

@jamespack commented on GitHub (May 29, 2025):

Do we even do that kind of book keeping?

@jamespack commented on GitHub (May 29, 2025): Do we even do that kind of book keeping?

claunia commented

@vadimkantorov commented on GitHub (May 29, 2025):

Well, there is already a "destructive" option to close the tab (and restart the tab when the user wishes so isn't much different) , so the bookkeeping should be somewhere...

@vadimkantorov commented on GitHub (May 29, 2025): Well, there is already a "destructive" option to close the tab (and restart the tab when the user wishes so isn't much different) , so the bookkeeping should be somewhere...

claunia commented

@jamespack commented on GitHub (Jun 16, 2025):

Sure just destroying and re-creating the tab would be fairly trivial (I think). Btw there is a setting currently available to always create new tabs next to the current tab instead of at the end of the tab row which is the default. Not sure if you were aware of that or not. That would solve at least part of this.

@jamespack commented on GitHub (Jun 16, 2025): Sure just destroying and re-creating the tab would be fairly trivial (I think). Btw there is a setting currently available to always create new tabs next to the current tab instead of at the end of the tab row which is the default. Not sure if you were aware of that or not. That would solve at least part of this.

claunia commented