Add a feature/option to automatically relaunch terminated profiles (vs closeOnExit) #6698

Closed
opened 2026-01-31 00:45:06 +00:00 by claunia · 4 comments
Owner

Originally created by @vlork on GitHub (Mar 2, 2020).

Description of the new feature/enhancement

Automatically attempt to reconnect terminated sessions.

Proposed technical implementation details (optional)

In profiles.json, profile.closeOnExit, add a "reconnect" option that automatically reconnects a terminated session alternatively keeps attempting to do so every, say, ten seconds until connection is made or tab is closed.

Description

When I wake up my computer from hibernation alternatively restart a remote server, I'd like to not have to manually reopen tabs.

Originally created by @vlork on GitHub (Mar 2, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement Automatically attempt to reconnect terminated sessions. <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> # Proposed technical implementation details (optional) In profiles.json, profile.closeOnExit, add a "reconnect" option that automatically reconnects a terminated session alternatively keeps attempting to do so every, say, ten seconds until connection is made or tab is closed. <!-- A clear and concise description of what you want to happen. --> # Description When I wake up my computer from hibernation alternatively restart a remote server, I'd like to not have to manually reopen tabs.
Author
Owner

@DHowett-MSFT commented on GitHub (Mar 5, 2020):

Thanks for the feature request! I've tagged it up into backlog.

@DHowett-MSFT commented on GitHub (Mar 5, 2020): Thanks for the feature request! I've tagged it up into backlog.
Author
Owner

@pernu commented on GitHub (Apr 15, 2020):

This would be a significant quality of life improvement.

I think the profile setting should take a couple of options, maybe something like "automatic" to work as the reporter described, and "manual", where the user would be required to hit the enter key to initiate the relaunch.

@pernu commented on GitHub (Apr 15, 2020): This would be a significant quality of life improvement. I think the profile setting should take a couple of options, maybe something like "automatic" to work as the reporter described, and "manual", where the user would be required to hit the enter key to initiate the relaunch.
Author
Owner

@zadjii-msft commented on GitHub (Feb 9, 2021):

You know what, I think this is actually the same thing as #4379 "Feature Request: option to relaunch a profile when it exits". I'm gonna use that as the megathread for tracking this (and related) issues for now. Thanks!

/dup #4379

@zadjii-msft commented on GitHub (Feb 9, 2021): You know what, I think this is actually the same thing as #4379 "Feature Request: option to relaunch a profile when it exits". I'm gonna use that as the megathread for tracking this (and related) issues for now. Thanks! /dup #4379
Author
Owner

@ghost commented on GitHub (Feb 9, 2021):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Feb 9, 2021): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#6698