Session management support #22018

Closed
opened 2026-01-31 08:01:05 +00:00 by claunia · 3 comments
Owner

Originally created by @weironz on GitHub (Jul 28, 2024).

Description of the new feature/enhancement

Proposed technical implementation details (optional)

Is it possible to support saving historical session connections, because if there are dozens of sessions, it would be very time consuming to manually enter the address each time to connect remotely.

like this:
image

Originally created by @weironz on GitHub (Jul 28, 2024). # Description of the new feature/enhancement # Proposed technical implementation details (optional) Is it possible to support saving historical session connections, because if there are dozens of sessions, it would be very time consuming to manually enter the address each time to connect remotely. like this: ![image](https://github.com/user-attachments/assets/4b208776-dffe-4c09-9d4c-9eb307f4b36a)
Author
Owner

@lhecker commented on GitHub (Jul 29, 2024):

Is there a reason why your shell's command history is insufficient for this?

@lhecker commented on GitHub (Jul 29, 2024): Is there a reason why your shell's command history is insufficient for this?
Author
Owner

@zadjii-msft commented on GitHub (Jul 29, 2024):

You can always make profiles for each of these. You can then also group them into folders in the newTabMenu.

There is the "auto-detect profiles from .ssh/config" feature (#9031), which never got finished (#15007). But that would auto-generate profiles from the hosts in .ssh/config.

Or I suppose in 1.22 you could add a .wt.json file to your %userprofile% that's got a snippet for each connection. So you could have something like:

{
    "$version": "1.0.0",
    "snippets":
    [
        {
            "input": "ssh 192.168.0.1",
            "name": "my thing",
            "description": "ssh to my thing"
        },
        {
            "input": "ssh 192.168.0.2",
            "name": "another one",
            "description": "you get the picture"
        },
    ]
}

(previous discussion: #13327)

@zadjii-msft commented on GitHub (Jul 29, 2024): You can always make [profiles](https://learn.microsoft.com/en-us/windows/terminal/customize-settings/profile-general) for each of these. You can then also group them into folders in the [newTabMenu](https://learn.microsoft.com/en-us/windows/terminal/customize-settings/appearance#new-tab-dropdown). There is the "auto-detect profiles from `.ssh/config`" feature (#9031), which never got finished (#15007). But that would auto-generate profiles from the hosts in `.ssh/config`. Or I suppose in 1.22 you could add a `.wt.json` file to your `%userprofile%` that's got a snippet for each connection. So you could have something like: ```json { "$version": "1.0.0", "snippets": [ { "input": "ssh 192.168.0.1", "name": "my thing", "description": "ssh to my thing" }, { "input": "ssh 192.168.0.2", "name": "another one", "description": "you get the picture" }, ] } ``` (previous discussion: #13327)
Author
Owner

@microsoft-github-policy-service[bot] commented on GitHub (Aug 2, 2024):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@microsoft-github-policy-service[bot] commented on GitHub (Aug 2, 2024): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**. <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#22018