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

Feature Request : enable WinRM or PowerShell Remoting connections #3310

New Issue
Open
opened 2026-01-30 23:18:19 +00:00 by claunia · 0 comments
claunia commented 2026-01-30 23:18:19 +00:00
Owner
Copy Link

Originally created by @RoguePointer80 on GitHub (Aug 8, 2019).

Description of the new feature/enhancement

For remote Windows computers, like Azure VM (or other cloud providers), there is no direct way to have a remote terminal. Automation tools like Hashicorp Packer rely on WinRM, also known as PowerShell Remoting, to send powershell commands and receive the output.
It would be a great productivity improvement to have a new connection type (similar to the Azure Cloud Shell), which would connect to a remote computer securely using WinRM and provide a shell. With the current ability to have tabs in Windows Terminal, a developer could have in the same app multiple shells on multiple computers. Think of it like Remote Desktop Connection Manager, but for terminals instead of GUI.
This is related to issues #555 and #626.

Proposed technical implementation details (optional)

In addition to the curren azure cloud shell connection type, add a new type called for WinRM. When the profile contains this particular guid, launch a new WinRM client. As for the connection settings like the remote host address, username/password etc, this could either be parsed from the "commandline" profile property, or add a new profile property called "connectionspecific", which would be a json object that is passed down to the specific connection being created.

I believe the WinRM client components are part of Windows, so that wouldn't be too much of a problem to use.

Originally created by @RoguePointer80 on GitHub (Aug 8, 2019). # Description of the new feature/enhancement For remote Windows computers, like Azure VM (or other cloud providers), there is no direct way to have a remote terminal. Automation tools like Hashicorp Packer rely on WinRM, also known as PowerShell Remoting, to send powershell commands and receive the output. It would be a great productivity improvement to have a new connection type (similar to the Azure Cloud Shell), which would connect to a remote computer securely using WinRM and provide a shell. With the current ability to have tabs in Windows Terminal, a developer could have in the same app multiple shells on multiple computers. Think of it like Remote Desktop Connection Manager, but for terminals instead of GUI. This is related to issues #555 and #626. # Proposed technical implementation details (optional) In addition to the curren azure cloud shell connection type, add a new type called for WinRM. When the profile contains this particular guid, launch a new WinRM client. As for the connection settings like the remote host address, username/password etc, this could either be parsed from the "commandline" profile property, or add a new profile property called "connectionspecific", which would be a json object that is passed down to the specific connection being created. I believe the WinRM client components are part of Windows, so that wouldn't be too much of a problem to use.
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-Fix labels 2026-01-30 23:18:19 +00:00
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 Needs-Tag-Fix 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#3310
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?