starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Ability to group profiles #20255

New Issue
Closed
opened 2026-01-31 07:08:11 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 07:08:11 +00:00
Owner
Copy Link

Originally created by @chadleywilson on GitHub (Jul 18, 2023).

I am not sure if this can already be done, but I could not find the correct search term for it, and apologise in advance if need be.

I have a lot of connection profiles (200+), MS Terminal makes it so much easier to manage them, but could use refinement, scrolling through the list can waste time some days.

Most of my connections are are ssh connections to docker swarms or kubernetes clusters. see my example below.

It would be nice if I could group my connections by cluster or server purpose them and have "sub menus" to better organise these.

Proposed technical implementation details (optional)

Here is sort of a summarized example, a typical cluster would have about 7 servers minimum. This is 3 server cluster example actually names changed and guids probably nonsense as I changed them slightly for the demonstration here , I was thinking something along these lines to group them.

       {
           "groupNameorTag": "Cluster A"
           "Description": "all Cluster A masters and nodes"
         {
                "colorScheme": "Raspberry",
                "commandline": "ssh ubuntu@mst-01",
                "guid": "{4268914b-3bba-5c19-be6f-42893bc5a277}",
                "hidden": false,
                "icon": "C:\\Scripts\\windows-terminal-icons\\icons\\ubuntu.png",
                "name": "ssh mst-01",
                "tabTitle": "mst-01"
            }'
             {
                "colorScheme": "Raspberry",
                "commandline": "ssh ubuntu@node-01",
                "guid": "{4268914b-3bba-5c19-be6f-42893bc5a278}",
                "hidden": false,
                "icon": "C:\\Scripts\\windows-terminal-icons\\icons\\ubuntu.png",
                "name": "ssh node-01",
                "tabTitle": "node-01"
            }'
             {
                "colorScheme": "Raspberry",
                "commandline": "ssh ubuntu@node-0",
                "guid": "{4268914b-3bba-5c19-be6f-42893bc5a279}",
                "hidden": false,
                "icon": "C:\\Scripts\\windows-terminal-icons\\icons\\ubuntu.png",
                "name": "ssh node-02",
                "tabTitle": "node-02"
            }
        }

When you click the drop down arrow, instead of only seeing PowerShell/ cmd / azure cloud shell / PowerShell 7 standard profiles, I would like to be able to have sub menus for docker swarms and Kubernetes clusters and categorize some of the stand alone servers that I connect to on a daily basis.

I have shortened and redacted version attached as a pic, which I took from a older user profile, but it should be enough illustrate what my colleagues and I use on a daily basis.

image

Originally created by @chadleywilson on GitHub (Jul 18, 2023). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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! --> I am not sure if this can already be done, but I could not find the correct search term for it, and apologise in advance if need be. I have a lot of connection profiles (200+), MS Terminal makes it so much easier to manage them, but could use refinement, scrolling through the list can waste time some days. Most of my connections are are ssh connections to docker swarms or kubernetes clusters. see my example below. It would be nice if I could group my connections by cluster or server purpose them and have "sub menus" to better organise these. # Proposed technical implementation details (optional) Here is sort of a summarized example, a typical cluster would have about 7 servers minimum. This is 3 server cluster example actually names changed and guids probably nonsense as I changed them slightly for the demonstration here , I was thinking something along these lines to group them. ``` { "groupNameorTag": "Cluster A" "Description": "all Cluster A masters and nodes" { "colorScheme": "Raspberry", "commandline": "ssh ubuntu@mst-01", "guid": "{4268914b-3bba-5c19-be6f-42893bc5a277}", "hidden": false, "icon": "C:\\Scripts\\windows-terminal-icons\\icons\\ubuntu.png", "name": "ssh mst-01", "tabTitle": "mst-01" }' { "colorScheme": "Raspberry", "commandline": "ssh ubuntu@node-01", "guid": "{4268914b-3bba-5c19-be6f-42893bc5a278}", "hidden": false, "icon": "C:\\Scripts\\windows-terminal-icons\\icons\\ubuntu.png", "name": "ssh node-01", "tabTitle": "node-01" }' { "colorScheme": "Raspberry", "commandline": "ssh ubuntu@node-0", "guid": "{4268914b-3bba-5c19-be6f-42893bc5a279}", "hidden": false, "icon": "C:\\Scripts\\windows-terminal-icons\\icons\\ubuntu.png", "name": "ssh node-02", "tabTitle": "node-02" } } ``` <!-- A clear and concise description of what you want to happen. --> When you click the drop down arrow, instead of only seeing PowerShell/ cmd / azure cloud shell / PowerShell 7 standard profiles, I would like to be able to have sub menus for docker swarms and Kubernetes clusters and categorize some of the stand alone servers that I connect to on a daily basis. I have shortened and redacted version attached as a pic, which I took from a older user profile, but it should be enough illustrate what my colleagues and I use on a daily basis. ![image](https://github.com/microsoft/terminal/assets/43165291/f60c7dd0-547c-4311-b47f-09cbff4f7efc)
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 07:08:11 +00:00
claunia commented 2026-01-31 07:08:12 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 18, 2023):

quick note: we introduced newTabMenu in 1.17. See #1571. There's no docs for it yet though 😢

I'll make a longer reply later

@zadjii-msft commented on GitHub (Jul 18, 2023): quick note: we introduced `newTabMenu` in 1.17. See #1571. There's no docs for it yet though 😢 I'll make a longer reply later
claunia commented 2026-01-31 07:08:12 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 19, 2023):

Alright, we've got a docs PR out now: https://github.com/MicrosoftDocs/terminal/pull/692

technically, this is a /dup of #1571, so I'll close it as such.

Thanks for giving me the impetus to finally document that!

@zadjii-msft commented on GitHub (Jul 19, 2023): Alright, we've got a docs PR out now: https://github.com/MicrosoftDocs/terminal/pull/692 technically, this is a /dup of #1571, so I'll close it as such. Thanks for giving me the impetus to finally document that!
claunia commented 2026-01-31 07:08:12 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Jul 19, 2023):

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!

@microsoft-github-policy-service[bot] commented on GitHub (Jul 19, 2023): 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.
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 Issue-Feature Resolution-Duplicate
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#20255
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?