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

Workspaces / Open a group of tabs at one time #21548

New Issue
Open
opened 2026-01-31 07:47:52 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 07:47:52 +00:00
Owner
Copy Link

Originally created by @roberttco on GitHub (Apr 18, 2024).

Description of the new feature/enhancement

I would like to be able to open multiple tabs (a collection of tabs) at one time - much like opening a saved collection in Edge. It would be nice if each tab had the same look/feel.

Proposed technical implementation details (optional)

At ahigh level, this feature would include:

  • easily adding a tab to a collection - right click and in the tab's settings through a collection dropdown.
  • easily remove a tab from a collection.
  • assign the same look/feel to each tab in a collection (collection appearance?)
  • open tabs not already open in the collection (e.g. don't open a new tab if one is already open and it belongs to the collection).
Originally created by @roberttco on GitHub (Apr 18, 2024). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 I would like to be able to open multiple tabs (a collection of tabs) at one time - much like opening a saved collection in Edge. It would be nice if each tab had the same look/feel. # Proposed technical implementation details (optional) At ahigh level, this feature would include: - easily adding a tab to a collection - right click and in the tab's settings through a collection dropdown. - easily remove a tab from a collection. - assign the same look/feel to each tab in a collection (collection appearance?) - open tabs not already open in the collection (e.g. don't open a new tab if one is already open and it belongs to the collection).
claunia added the Issue-FeatureProduct-TerminalArea-UserInterfaceIssue-Scenario labels 2026-01-31 07:47:53 +00:00
claunia commented 2026-01-31 07:47:53 +00:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 18, 2024):

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@github-actions[bot] commented on GitHub (Apr 18, 2024): Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! ### Closed similar issues: - [Allow users to create a 'collection' of tabs that will open specified command lines with different starting directories. (#6851)](https://github.com/microsoft/terminal/issues/6851), similarity score: 0.82 - [Save and open group of tabs in specific directories on single-click (#10565)](https://github.com/microsoft/terminal/issues/10565), similarity score: 0.79 > Note: You can give me feedback by thumbs upping or thumbs downing this comment.
claunia commented 2026-01-31 07:47:54 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 18, 2024):

GUYS THIS IS NOW THE WORKSPACES THREAD. I've been thinking about this for a while now, and I'm super on board.

(also previously discussed in https://github.com/microsoft/terminal/issues/16502#issuecomment-1875636597)

Now, you can absolutely already do something kinda like this with the multipleActions action. But that's not super well exposed, and it's clunky.

I've been now really thinking for a while about "workspaces" for the Terminal. Or like, named windows. Each would have a set of tabs, and restore separately. And if you closed a named window, then we'd persist that name separately, and allow it to be restored simply.

(I've been using workspaces in Edge way too much recently and can't get over how useful they are)

@zadjii-msft commented on GitHub (Apr 18, 2024): GUYS THIS IS NOW THE WORKSPACES THREAD. I've been thinking about this for a while now, and I'm super on board. (also previously discussed in https://github.com/microsoft/terminal/issues/16502#issuecomment-1875636597) Now, you can absolutely already do something kinda like this with the `multipleActions` action. But that's not super well exposed, and it's clunky. I've been now really thinking for a while about "workspaces" for the Terminal. Or like, named windows. Each would have a set of tabs, and restore separately. And if you closed a named window, then we'd persist that name separately, and allow it to be restored simply. (I've been using workspaces in Edge way too much recently and can't get over how useful they are)
claunia commented 2026-01-31 07:47:54 +00:00
Author
Owner
Copy Link

@mian196 commented on GitHub (Dec 4, 2025):

Any update on this?

@mian196 commented on GitHub (Dec 4, 2025): Any update on this?
claunia commented 2026-01-31 07:47:55 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 5, 2025):

Nope. Someone just needs to write the code at this point.

It shouldn't be too hard to add logic such that:

  • When a named window is closed, we always persist that state to some new collection in state.json
  • we don't discard buffers from named windows persisted in this way
  • opening a window with a given name always restores its state

that would be a fantastic POC for a start here. Then you could add a button to the titlebar that:

  • lets you name the current window (if it doesn't have one)
  • list the persisted windows (workspaces)
    • opens that workspace if you click on it
  • and displays the current window name if this window has one

This would also pair incredibly with #9992

@zadjii-msft commented on GitHub (Dec 5, 2025): Nope. Someone just needs to write the code at this point. It shouldn't be too hard to add logic such that: * When a named window is closed, we always persist that state to some new collection in `state.json` * we don't discard buffers from named windows persisted in this way * opening a window with a given name always restores its state that would be a fantastic POC for a start here. Then you could add a button to the titlebar that: * lets you name the current window (if it doesn't have one) * list the persisted windows (workspaces) * opens that workspace if you click on it * and displays the current window name if this window has one ------------------ This would also pair _incredibly_ with #9992
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 Area-UserInterface Issue-Feature Issue-Scenario Product-Terminal
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#21548
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?