starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Feature Request: restart/reload terminal #19926

New Issue
Open
opened 2026-01-31 06:57:38 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 06:57:38 +00:00
Owner
Copy Link

Originally created by @sparkchaser on GitHub (May 23, 2023).

It would be helpful if a terminal session could be re-started in situ after it closes.

Background:
I build firmware for embedded devices that I control via SSH. I set up a terminal profile that runs the command ssh.exe <IP> <args>, so now I can open a shell and connect to the device's console with just a keystroke. Everything works great, at least until I flash a new firmware image and the device reboots. The underlying ssh process terminates and I get the "process exited" message. That terminal tab is effectively dead and I have to open a new tab to reconnect. If I try to connect before the device is ready, the ssh command in the new tab will time out and I'll have another dead terminal window to close and re-open. Re-connecting to the device and cleaning up all the old terminal windows is a multi-step process, and I often have to do this every 10-15 minutes. It's even more annoying when using quake mode (which I am now addicted to) since the tabs aren't visible.

It would be extremely helpful if in cases like this there was a command to reuse the existing terminal window and re-start that session from scratch. Disconnect the dead process from the terminal, run the terminal's command again, and attach the new process to the existing terminal instead of spawning a new one. PuTTY has a "restart session" command that does exactly this, and it makes it much easier to work with remote devices that reboot or otherwise drop connection. Being able to restart the process and reconnect to the device with a keystroke or context menu option would make my workflow a lot smoother. Retaining the existing scrollback buffer would be a nice bonus, but that's certainly not a requirement.

Originally created by @sparkchaser on GitHub (May 23, 2023). It would be helpful if a terminal session could be re-started in situ after it closes. Background: I build firmware for embedded devices that I control via SSH. I set up a terminal profile that runs the command `ssh.exe <IP> <args>`, so now I can open a shell and connect to the device's console with just a keystroke. Everything works great, at least until I flash a new firmware image and the device reboots. The underlying ssh process terminates and I get the "process exited" message. That terminal tab is effectively dead and I have to open a new tab to reconnect. If I try to connect before the device is ready, the ssh command in the new tab will time out and I'll have *another* dead terminal window to close and re-open. Re-connecting to the device and cleaning up all the old terminal windows is a multi-step process, and I often have to do this every 10-15 minutes. It's even more annoying when using quake mode (which I am now addicted to) since the tabs aren't visible. It would be extremely helpful if in cases like this there was a command to reuse the existing terminal window and re-start that session from scratch. Disconnect the dead process from the terminal, run the terminal's command again, and attach the new process to the *existing* terminal instead of spawning a new one. PuTTY has a "restart session" command that does exactly this, and it makes it much easier to work with remote devices that reboot or otherwise drop connection. Being able to restart the process and reconnect to the device with a keystroke or context menu option would make my workflow a lot smoother. Retaining the existing scrollback buffer would be a nice bonus, but that's certainly not a requirement.
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 06:57:38 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Attention Needs-Tag-Fix Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#19926
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?