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

Add option to add Windows Terminal to File Explorer #12005

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

Originally created by @AraHaan on GitHub (Jan 10, 2021).

Description of the new feature/enhancement

I would like all of the places where the user can open powershell (from shift right click on File Explorer), and on the File Tab on file explorer to be replaced or add options to those 2 places in File Explorer on Windows 10 (even on the Windows Store terminals).
Or at least a button that says open [insert program here] here inside Windows Terminal. Where it does what it would normally do but make it inside of the current Windows Terminal instance (or make a new one if there is no current instance of Windows Terminal).

Proposed technical implementation details (optional)

I would like this because currently it only lists the powershell built into windows in File Explorer, but what if I want to use tabs instead from Windows Terminal to only worry about 1 process only that holds then all of the consoles I want to be running.

Originally created by @AraHaan on GitHub (Jan 10, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 all of the places where the user can open powershell (from shift right click on File Explorer), and on the File Tab on file explorer to be replaced or add options to those 2 places in File Explorer on Windows 10 (even on the Windows Store terminals). Or at least a button that says ``open [insert program here] here inside Windows Terminal``. Where it does what it would normally do but make it inside of the current Windows Terminal instance (or make a new one if there is no current instance of Windows Terminal). <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> # Proposed technical implementation details (optional) I would like this because currently it only lists the powershell built into windows in File Explorer, but what if I want to use tabs instead from Windows Terminal to only worry about 1 process only that holds then all of the consoles I want to be running. <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 03:03:44 +00:00
claunia commented 2026-01-31 03:03:44 +00:00
Author
Owner
Copy Link

@KalleOlaviNiemitalo commented on GitHub (Jan 10, 2021):

I want to use tabs instead from Windows Terminal to only worry about 1 process only

Running PowerShell in Windows Terminal needs more processes than running it in the default conhost. It needs a powershell.exe or pwsh.exe process as usual, then a OpenConsole.exe process instead of conhost.exe, and an extra WindowsTerminal.exe process. https://github.com/microsoft/terminal/pull/7240 even describes a plan to add a "content process" for each session.

@KalleOlaviNiemitalo commented on GitHub (Jan 10, 2021): > I want to use tabs instead from Windows Terminal to only worry about 1 process only Running PowerShell in Windows Terminal needs _more_ processes than running it in the default conhost. It needs a powershell.exe or pwsh.exe process as usual, then a OpenConsole.exe process instead of conhost.exe, and an extra WindowsTerminal.exe process. <https://github.com/microsoft/terminal/pull/7240> even describes a plan to add a "content process" for each session.
claunia commented 2026-01-31 03:03:45 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 11, 2021):

Also, /dup #5591. 😄

@DHowett commented on GitHub (Jan 11, 2021): Also, /dup #5591. :smile:
claunia commented 2026-01-31 03:03:45 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 11, 2021):

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!

@ghost commented on GitHub (Jan 11, 2021): 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!
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#12005
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?