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

WT_SESSION is not set immediately #20705

New Issue
Closed
opened 2026-01-31 07:21:44 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 07:21:44 +00:00
Owner
Copy Link

Originally created by @kaneryu on GitHub (Oct 21, 2023).

Windows Terminal version

1.18.1421.0

Windows build number

10.0.19042

Other Software

The code that is mentioned in the steps:

choice /M "Would you like to start WindowsTerminal?"
echo %WT_SESSION%
IF "%WT_SESSION%"=="%WT_SESSION%" (
IF %ERRORLEVEL% EQU 1 start %userprofile%\Downloads\terminal-1.18.1421.0\WindowsTerminal.exe && exit
)

cls && cls

Steps to reproduce

Note: This code is being run through the AutoRun reg key. It runs as soon as any conhost is opened.

Run the above code in WT
%WT_SESSION% Is not set

Expected Behavior

%WT_SESSION% Is set

Actual Behavior

%WT_SESSION% Is not set

I would assume that the code runs before anything WT related even starts up, because after selecting N and checking the value of %WT_SESSION%, it has been set.

I have seen other threads mentioning that %WT_SESSION% should not be used to check if you can use certain capabilities of the terminal, however, I just want to check if it's running, I don't care about the capabilities of the terminal. Is there another way to check this?

Originally created by @kaneryu on GitHub (Oct 21, 2023). ### Windows Terminal version 1.18.1421.0 ### Windows build number 10.0.19042 ### Other Software The code that is mentioned in the steps: choice /M "Would you like to start WindowsTerminal?" echo %WT_SESSION% IF "%WT_SESSION%"=="%WT_SESSION%" ( IF %ERRORLEVEL% EQU 1 start %userprofile%\Downloads\terminal-1.18.1421.0\WindowsTerminal.exe && exit ) cls && cls ### Steps to reproduce Note: This code is being run through the AutoRun reg key. It runs as soon as any conhost is opened. Run the above code in WT %WT_SESSION% Is not set ### Expected Behavior %WT_SESSION% Is set ### Actual Behavior %WT_SESSION% Is not set I would assume that the code runs _before_ anything WT related even starts up, because after selecting N and checking the value of %WT_SESSION%, it has been set. I have seen other threads mentioning that %WT_SESSION% should not be used to check if you can use certain capabilities of the terminal, however, I just want to check if it's running, I don't care about the capabilities of the terminal. Is there another way to check this?
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 07:21:44 +00:00
claunia commented 2026-01-31 07:21:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 23, 2023):

I'm guessing this is something like #13006. You're starting some console process (cmd.exe, your batch script, whatever) directly, and then that's getting handed-off to the Windows Terminal (the configured default terminal) rather than conhost. Does that sound right/?

Terminal never has a chance to set WT_SESSION in that scenario - cmd.exe spawned and got its env vars before it knew it would be attached to a Terminal.

@zadjii-msft commented on GitHub (Oct 23, 2023): I'm guessing this is something like #13006. You're starting _some console process_ (cmd.exe, your batch script, whatever) directly, and then that's getting handed-off to the Windows Terminal (the configured default terminal) rather than conhost. Does that sound right/? Terminal never has a chance to set `WT_SESSION` in that scenario - `cmd.exe` spawned and got its env vars before it knew it would be attached to a Terminal.
claunia commented 2026-01-31 07:21:45 +00:00
Author
Owner
Copy Link

@kaneryu commented on GitHub (Oct 24, 2023):

Yes (however the handoff isn't automatic). The reason why i would want to be able to read WT session immediatly is to see if the current console is open in WT or not.
However I understand how the autorun would run it before the WT_SESSION was able to be set.
I'm going to close this issue, becauase I don't think i will end up doing it this way (i'll probably find another non-admin way to make WT the default terminal application) because the current method messes up with cmd windows that other applications open. Thank you for responding too this

@kaneryu commented on GitHub (Oct 24, 2023): Yes (however the handoff isn't automatic). The reason why i would want to be able to read WT session immediatly is to see if the current console is open in WT or not. However I understand how the autorun would run it before the WT_SESSION was able to be set. I'm going to close this issue, becauase I don't think i will end up doing it this way (i'll probably find another non-admin way to make WT the default terminal application) because the current method messes up with cmd windows that other applications open. Thank you for responding too this
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-Bug Needs-Attention Needs-Triage
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#20705
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?