starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Don't close Terminal upon closing the last tab #22114

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

Originally created by @Cellhawk on GitHub (Aug 20, 2024).

Description of the new feature/enhancement

As it is with most modern applications that use tabs, these days, like web browsers or even text editors (e.g. vscode), you can usually close all tabs without having to close the app itself.

Allow us to close tabs without closing the Windows Terminal app itself.

As someone, who works with a lot of different cmd tabs with different env variables, closing and opening new tabs relatively often, using .cmd files, I would find this extremely helpful and workflow-friendly, as I sometimes end up with all tabs closed, but want to keep the terminal open on my workstation.

Proposed technical implementation details

An option in settings to disable closing of the entire Terminal, when closing the last tab. Closing the last tab would put the user on a simple landing screen, akin to modern browsers, but much less busy, if not outright empty.

The "landing screen" that appears when all tabs are closed could be an empty window with either "Defaults" appearance settings, or a custom profile with custom settings.

An option to set the landing screen as default profile when opening Windows Terminal. (ideally just when opening Windows Terminal, not when clicking the + button, as that feels useless)

In the long run, the landing screen could be expanded upon to contain more content for convenience and better workflow.

Originally created by @Cellhawk on GitHub (Aug 20, 2024). ### Description of the new feature/enhancement As it is with most modern applications that use tabs, these days, like web browsers or even text editors (e.g. vscode), you can usually close all tabs without having to close the app itself. Allow us to close tabs without closing the Windows Terminal app itself. _As someone, who works with a lot of different cmd tabs with different env variables, closing and opening new tabs relatively often, using .cmd files, I would find this extremely helpful and workflow-friendly, as I sometimes end up with all tabs closed, but want to keep the terminal open on my workstation._ ___ ### Proposed technical implementation details An option in settings to disable closing of the entire Terminal, when closing the last tab. Closing the last tab would put the user on a simple landing screen, akin to modern browsers, but much less busy, if not outright empty. The "landing screen" that appears when all tabs are closed could be an empty window with either "Defaults" appearance settings, or a custom profile with custom settings. An option to set the landing screen as default profile when opening Windows Terminal. (ideally just when opening Windows Terminal, *not* when clicking the + button, as that feels useless) In the long run, the landing screen could be expanded upon to contain more content for convenience and better workflow.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 08:03:47 +00:00
claunia commented 2026-01-31 08:03:48 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 20, 2024):

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #6276 for more discussion.

/dup #6276

@zadjii-msft commented on GitHub (Aug 20, 2024): Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #6276 for more discussion. /dup #6276
claunia commented 2026-01-31 08:03:48 +00:00
Author
Owner
Copy Link

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

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 (Aug 20, 2024): 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! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
claunia commented 2026-01-31 08:03:48 +00:00
Author
Owner
Copy Link

@Cellhawk commented on GitHub (Aug 20, 2024):

Aw shucks, I tried searching but somehow failed to find that. Thanks!

@Cellhawk commented on GitHub (Aug 20, 2024): Aw shucks, I tried searching but somehow failed to find that. Thanks!
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#22114
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?