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

Forced default profile tab, no matter what (when wt is the default terminal application) #23390

New Issue
Closed
opened 2026-01-31 08:40:53 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 08:40:53 +00:00
Owner
Copy Link

Originally created by @AbraxasDMG on GitHub (Jun 25, 2025).

Hi everyone,

This might be intended behavior but I need to ask anyway.

Whenever I start wt (preview) from the command line, if there is no wt already running, a window will be created with an empty default profile, irrelevant of what was supplied at the command line.

This is happening in case that the wt is set as the default terminal application.

So, if I execute wt -p cmd (for command prompt), a window will pop up with a default tab (for pwsh in my case0 and with cmd tab.
Even if I execute wt -p pwsh (which is a default profile), there will be 2 pwsh tabs.

If this is indeed an intended behavior, is there a workaround to avoid the creation of this default profile tab?

Thanks in advance!

Originally created by @AbraxasDMG on GitHub (Jun 25, 2025). Hi everyone, This might be intended behavior but I need to ask anyway. Whenever I start wt (preview) from the command line, if there is no wt already running, a window will be created with an empty default profile, irrelevant of what was supplied at the command line. This is happening in case that the wt is set as the default terminal application. So, if I execute wt -p cmd (for command prompt), a window will pop up with a default tab (for pwsh in my case0 and with cmd tab. Even if I execute wt -p pwsh (which is a default profile), there will be 2 pwsh tabs. If this is indeed an intended behavior, is there a workaround to avoid the creation of this default profile tab? Thanks in advance!
claunia commented 2026-01-31 08:40:54 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 2, 2025):

Interesting!

  • What version of Terminal are you using? You can check with wt -v.
  • Are you by chance using one of the persistence options such as "restore windows from last session"?
  • If you open the folder containing settings.json, do you have a bunch of buffer state files laying around/?

Image

@DHowett commented on GitHub (Jul 2, 2025): _Interesting!_ - What version of Terminal are you using? You can check with `wt -v`. - Are you by chance using one of the persistence options such as "restore windows from last session"? - If you open the folder containing settings.json, do you have a bunch of buffer state files laying around/? ![Image](https://github.com/user-attachments/assets/c65bcdfc-0844-435d-aec3-48aaa7893094)
claunia commented 2026-01-31 08:40:54 +00:00
Author
Owner
Copy Link

@AbraxasDMG commented on GitHub (Jul 2, 2025):

Hi.

  • It's the WT Preview v1.23.11752.0 on Windows 11.
  • The "When terminal starts" option is set to "Open tab with the default profile" (it's the only other available option aside from "Open windows from a previous session").
  • Aside from the settings.json, there is one state.json file in that folder. File modification time differs by 1 second (state.json +1 second).
@AbraxasDMG commented on GitHub (Jul 2, 2025): Hi. - It's the WT Preview v1.23.11752.0 on Windows 11. - The "When terminal starts" option is set to "Open tab with the default profile" (it's the only other available option aside from "Open windows from a previous session"). - Aside from the settings.json, there is one state.json file in that folder. File modification time differs by 1 second (state.json +1 second).
claunia commented 2026-01-31 08:40:55 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Aug 13, 2025):

Thanks for getting back to us. A fix should be available on the Canary channel, which can be found here: https://github.com/microsoft/terminal?tab=readme-ov-file#installing-windows-terminal-canary

We also backported the fixes to v1.23, so it should be available on the lastest v1.23 release.

Can you confirm if that fixed your issue/?

@carlos-zamora commented on GitHub (Aug 13, 2025): Thanks for getting back to us. A fix should be available on the Canary channel, which can be found here: https://github.com/microsoft/terminal?tab=readme-ov-file#installing-windows-terminal-canary We also backported the fixes to v1.23, so it should be available on the lastest v1.23 release. Can you confirm if that fixed your issue/?
claunia commented 2026-01-31 08:40:55 +00:00
Author
Owner
Copy Link

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

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 18, 2025): 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.
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 Needs-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity
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#23390
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?