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

Attaching of externally existing terminal #15410

New Issue
Closed
opened 2026-01-31 04:37:49 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 04:37:49 +00:00
Owner
Copy Link

Originally created by @SebastianSolidwork on GitHub (Oct 1, 2021).

I want to be able to attach terminals which exist outside of WT.
Examples: log terminals from an application or terminals started through a file from the explorer

Examples of other software: ConEmu and Cmder are having such a function

Originally created by @SebastianSolidwork on GitHub (Oct 1, 2021). I want to be able to attach terminals which exist outside of WT. Examples: log terminals from an application or terminals started through a file from the explorer Examples of other software: ConEmu and Cmder are having such a function
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-FixProduct-Terminal labels 2026-01-31 04:37:49 +00:00
claunia commented 2026-01-31 04:37:50 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 21, 2021):

From @mjcarman in #11569

I migrated to Windows Terminal from ConEmu and one feature I miss is its "Attach to" function that captures an existing console window and moves it into the terminal as a tab. It's useful for managing windows that weren't — or more importantly, can't be — opened in the terminal.

Example 1: The launcher for the LynxOS development environment opens a bash console in the appropriate working directory and runs some setup commands it. I'd like to be able to move that console into Windows Terminal. (Replicating this via a WT profile is only partially possible, and even that much required a fair bit of sleuthing around to figure out.)

Example 2: Eclipse-based GUI applications can be launched with the console visible. Being able to move that console into WT would allow me to declutter my workspace.

I don't know if setting Windows Terminal as the default console host would alleviate these use cases. It might, but that feature is only available on Windows 11. This feature should work on any OS.

Proposed technical implementation details (optional)

The context menu for the title bar should have an "attach to" (or similarly named) option that opens a dialog of existing windows that may be captured and moved into Windows Terminal.

@zadjii-msft commented on GitHub (Oct 21, 2021): _From @mjcarman in #11569_ > I migrated to Windows Terminal from ConEmu and one feature I miss is its "Attach to" function that captures an existing console window and moves it into the terminal as a tab. It's useful for managing windows that weren't — or more importantly, can't be — opened in the terminal. > > Example 1: The launcher for the LynxOS development environment opens a bash console in the appropriate working directory and runs some setup commands it. I'd like to be able to move that console into Windows Terminal. (Replicating this via a WT profile is only partially possible, and even that much required a fair bit of sleuthing around to figure out.) > > Example 2: Eclipse-based GUI applications can be launched with the console visible. Being able to move that console into WT would allow me to declutter my workspace. > > I don't know if setting Windows Terminal as the default console host would alleviate these use cases. It might, but that feature is only available on Windows 11. This feature should work on any OS. > > # Proposed technical implementation details (optional) > The context menu for the title bar should have an "attach to" (or similarly named) option that opens a dialog of existing windows that may be captured and moved into Windows Terminal.
claunia commented 2026-01-31 04:37:50 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Mar 20, 2023):

Hi @SebastianSolidwork. Thanks for the feature request. We've discussed it as a team and we feel that tab tearout and default terminal are two features that are more relevant for day to day use cases. They don't necessarily fulfill all the requirements you specified, but they meet most of them.

@carlos-zamora commented on GitHub (Mar 20, 2023): Hi @SebastianSolidwork. Thanks for the feature request. We've discussed it as a team and we feel that tab tearout and default terminal are two features that are more relevant for day to day use cases. They don't necessarily fulfill all the requirements you specified, but they meet most of them.
claunia commented 2026-01-31 04:37:50 +00:00
Author
Owner
Copy Link

@SebastianSolidwork commented on GitHub (Mar 21, 2023):

I'm sad to read.
"they meet most of them."
Can you explain how?
Either I'm able to attach an external started console or not.

@SebastianSolidwork commented on GitHub (Mar 21, 2023): I'm sad to read. "they meet most of them." Can you explain how? Either I'm able to attach an external started console or not.
claunia commented 2026-01-31 04:37:51 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 21, 2023):

With the "default terminal" feature, CLI applications will boot into a Terminal window immediately, rather than a conhost window.

With tab tearout/reattach, those Terminal windows can be re-combined with other terminal windows.

Does that make sense?

@zadjii-msft commented on GitHub (Mar 21, 2023): With the "default terminal" feature, CLI applications will boot into a Terminal window immediately, rather than a conhost window. With tab tearout/reattach, those Terminal windows can be re-combined with other terminal windows. Does that make sense?
claunia commented 2026-01-31 04:37:51 +00:00
Author
Owner
Copy Link

@SebastianSolidwork commented on GitHub (Mar 21, 2023):

Thanks for the clarification! I did not know what default terminal meant.
I guess you are referring to this by the default terminal? https://devblogs.microsoft.com/commandline/windows-terminal-as-your-default-command-line-experience/
That would be sufficient for me.
But I have to wait until our IT rolls out Windows 11, we are still on 10.

@SebastianSolidwork commented on GitHub (Mar 21, 2023): Thanks for the clarification! I did not know what default terminal meant. I guess you are referring to this by the default terminal? https://devblogs.microsoft.com/commandline/windows-terminal-as-your-default-command-line-experience/ That would be sufficient for me. But I have to wait until our IT rolls out Windows 11, we are still on 10.
claunia commented 2026-01-31 04:37:51 +00:00
Author
Owner
Copy Link

@SebastianSolidwork commented on GitHub (Mar 22, 2023):

I got informed that our IT just now uninstalled all existing Windows 11 and replaced them by to Windows 10.
Therefore I will not get access to this feature soon. :-(

@SebastianSolidwork commented on GitHub (Mar 22, 2023): I got informed that our IT just now uninstalled all existing Windows 11 and replaced them by to Windows 10. Therefore I will not get access to this feature soon. :-(
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 Product-Terminal
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#15410
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?