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

Describe how to identity whether a PowerShell is running in Windows Terminal #7627

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

Originally created by @hahndorf on GitHub (Apr 24, 2020).

On the Windows Terminal User Documentation page /user-docs/index.md in the Tips and Tricks section, it says one should check for the environment variable WT_Session

When running a PowerShell in the terminal does indeed have this variable, but now run:

Start Powershell.exe

A new PowerShell Window is opened and it is not running in the new terminal, but it inherited the environment variables from its parent, so it also has WT_Session

So this method often works, but not always.

It would be nice to find out inside PowerShell whether it runs in the terminal?

This applies both to PowerShell 5.1 and 7

Originally created by @hahndorf on GitHub (Apr 24, 2020). <!-- Briefly describe which document needs to be corrected and why. --> On the Windows Terminal User Documentation page `/user-docs/index.md` in the Tips and Tricks section, it says one should check for the environment variable `WT_Session` When running a PowerShell in the terminal does indeed have this variable, but now run: Start Powershell.exe A new PowerShell Window is opened and it is not running in the new terminal, but it inherited the environment variables from its parent, so it also has `WT_Session` So this method often works, but not always. It would be nice to find out inside PowerShell whether it runs in the terminal? This applies both to PowerShell 5.1 and 7
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 01:08:55 +00:00
claunia commented 2026-01-31 01:08:56 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 24, 2020):

There is, by design, no reliable way. We have been hoping for someone to come along and explain what their use case would be for being able to determine that 😄

@DHowett-MSFT commented on GitHub (Apr 24, 2020): There is, by design, no reliable way. We have been hoping for someone to come along and explain what their use case would be for being able to determine that 😄
claunia commented 2026-01-31 01:08:57 +00:00
Author
Owner
Copy Link

@hahndorf commented on GitHub (Apr 24, 2020):

I can tell how I came across it. I do a lot of stuff in profiles, sometimes I want to reload a session (profile changed) or start a new session as a different user or elevated. I can figure out whether I am in PowerShell.exe or pwsh.exe and start the correct one. It would be nice to open a new session in the same "parent host" or even in a new tab of an existing terminal.

For now the tip is just not 100% correct.

@hahndorf commented on GitHub (Apr 24, 2020): I can tell how I came across it. I do a lot of stuff in profiles, sometimes I want to reload a session (profile changed) or start a new session as a different user or elevated. I can figure out whether I am in `PowerShell.exe` or `pwsh.exe` and start the correct one. It would be nice to open a new session in the same "parent host" or even in a new tab of an existing terminal. For now the tip is just not 100% correct.
claunia commented 2026-01-31 01:08:57 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 25, 2020):

So, anything we can do with environment variables is going to be subject to inheritance. The absolute most reliable thing to do will be to detect whether your shell's parent process is WindowsTerminal.exe -- we're not likely to change that name (but I make no promises).

In general, we're trying to go as long as possible not letting it be too easily detectable. We're supposed to be largely xterm-256color compatible, and given our shipping speed we absolutely don't want people working around perceived issues by heuristic detection because it can harm our ability to actually fix things.

In the future with #492 you won't need to make this decision (and all things should start in your preferred default terminal :P)

Marking Question/Answered but please feel free to continue the discussion.

@DHowett-MSFT commented on GitHub (Apr 25, 2020): So, anything we can do with environment variables is going to be subject to inheritance. The absolute most reliable thing to do will be to detect whether your shell's parent process is WindowsTerminal.exe -- we're not likely to change that name (but I make no promises). In general, we're trying to go as long as possible _not_ letting it be too easily detectable. We're supposed to be largely xterm-256color compatible, and given our shipping speed we absolutely don't want people working around perceived issues by heuristic detection because it can harm our ability to actually fix things. In the future with #492 you won't need to make this decision (and all things should start in your preferred default terminal :P) Marking Question/Answered but please feel free to continue the discussion.
claunia commented 2026-01-31 01:08:57 +00:00
Author
Owner
Copy Link

@mileso commented on GitHub (Jun 21, 2021):

There is, by design, no reliable way. We have been hoping for someone to come along and explain what their use case would be for being able to determine that 😄

I have a use case:

Set a different window title when running PowerShell within WIndows Terminal. Windows Terminal has less real estate because the title is displayed on a tab so I'd like to set a shorter title only when running under Windows Terminal.

Simple example: Add the path to the title only when not running within Windows Terminal.

@mileso commented on GitHub (Jun 21, 2021): > There is, by design, no reliable way. We have been hoping for someone to come along and explain what their use case would be for being able to determine that 😄 I have a use case: Set a different window title when running PowerShell within WIndows Terminal. Windows Terminal has less real estate because the title is displayed on a tab so I'd like to set a shorter title only when running under Windows Terminal. Simple example: Add the path to the title only when not running within Windows Terminal.
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-Question Needs-Tag-Fix Resolution-Answered
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#7627
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?