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

[PR #3858] Create Telnet connection type and default loopback profile for Universal #25533

New Issue
Open
opened 2026-01-31 09:10:07 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 09:10:07 +00:00
Owner
Copy Link

Original Pull Request: https://github.com/microsoft/terminal/pull/3858

State: closed
Merged: Yes

Summary of the Pull Request

For our Universal terminal for development purposes, we will use telnet to escape the universal application container and empower developers to debug/diagnose issues with their own machine on loopback to the already-elevated telnet context.

PR Checklist

  • Closes internal development-blocker deliverable
  • I work here
  • Manual testing
  • Internal tool right now to test the waters on what's possible, no public doc.
  • I'm a core contributor

Detailed Description of the Pull Request / Additional comments

We have two factors at odds here:

  1. To develop our modern devices platforms, our developers need the ability to run diagnostics and utilities directly on a device.
  2. Universal applications tend to be stuck inside a container

This provides a development-based way around the issue. The telnet server exists on a device when it is in a development mode and runs in an already elevated context. This is great for performing activities from off-device, but not for the same device. However, if we loopback out of the containered app to the elevated context, we should be able to be on-device but with the same power as off-device.

So overall, this adds the following:

  1. A telnet connection type, leveraging the MIT-licensed telnetpp library for the communication channel
  2. Telnet profile generators
  3. Customization of the universal-edition of settings loading so it goes directly into this telnet connection type
  4. A bunch of odds and ends cleaning up strings and handling errors and connection things (and icons and whatnot).

This enables a developer on a more constrained device that is set to developer mode to launch a special edition of Windows Terminal straight into a prompt that runs in an elevated context against the same device.

TODO:

  • Expose third-party notices in about box? @DHowett-MSFT
  • Upload telnetpp vcpkg to feed and update references
  • Do first pass PR on this myself then set to "ready" status from "draft"
  • Hookup resize
  • Make the tab say something
  • Telnet server detects this connection type and moves up to xterm256 utf-8 mode.

TODO after completion:

  • Ingest this package into development images of Windows

Validation Steps Performed

  • Connected from local dev box running this application in a containered context to the telnet server running on another device and ran commands.
  • Connected in loopback on the device itself to itself and ran commands.
**Original Pull Request:** https://github.com/microsoft/terminal/pull/3858 **State:** closed **Merged:** Yes --- ## Summary of the Pull Request For our Universal terminal for development purposes, we will use telnet to escape the universal application container and empower developers to debug/diagnose issues with their own machine on loopback to the already-elevated telnet context. ## PR Checklist * [x] Closes internal development-blocker deliverable * [x] I work here * [x] Manual testing * [x] Internal tool right now to test the waters on what's possible, no public doc. * [x] I'm a core contributor ## Detailed Description of the Pull Request / Additional comments We have two factors at odds here: 1. To develop our modern devices platforms, our developers need the ability to run diagnostics and utilities directly on a device. 2. Universal applications tend to be stuck inside a container This provides a development-based way around the issue. The telnet server exists on a device when it is in a development mode and runs in an already elevated context. This is great for performing activities from off-device, but not for the same device. However, if we loopback out of the containered app to the elevated context, we should be able to be on-device but with the same power as off-device. So overall, this adds the following: 1. A telnet connection type, leveraging the MIT-licensed telnetpp library for the communication channel 2. Telnet profile generators 3. Customization of the universal-edition of settings loading so it goes directly into this telnet connection type 4. A bunch of odds and ends cleaning up strings and handling errors and connection things (and icons and whatnot). This enables a developer on a more constrained device that is set to developer mode to launch a special edition of Windows Terminal straight into a prompt that runs in an elevated context against the same device. TODO: - [ ] Expose third-party notices in about box? @DHowett-MSFT - [x] Upload telnetpp vcpkg to feed and update references - [x] Do first pass PR on this myself then set to "ready" status from "draft" - [x] Hookup resize - [x] Make the tab say something - [ ] Telnet server detects this connection type and moves up to xterm256 utf-8 mode. TODO after completion: - [ ] Ingest this package into development images of Windows ## Validation Steps Performed - Connected from local dev box running this application in a containered context to the telnet server running on another device and ran commands. - [x] Connected in loopback on the device itself to itself and ran commands.
claunia added the pull-request label 2026-01-31 09:10:07 +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 pull-request
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#25533
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?