Expose the Tab Names through the UI API or Windows Envirnment variables #23541

Closed
opened 2026-01-31 08:45:20 +00:00 by claunia · 4 comments
Owner

Originally created by @eabase on GitHub (Aug 22, 2025).

Description of the new feature

I would like to access the actual names of the various Windows tabs using powershell.
We can get the PID's but since the names are not exposed, it's impossible to know what PID belongs to what tab.

The proposal is to expose the give terminal Tab Name to the API or OS environment.

Proposed technical implementation details

no idea.

Originally created by @eabase on GitHub (Aug 22, 2025). ### Description of the new feature I would like to access the actual names of the various Windows tabs using powershell. We can get the PID's but since the names are not exposed, it's impossible to know what PID belongs to what tab. The proposal is to expose the give terminal Tab **Name** to the API or OS environment. ### Proposed technical implementation details no idea.
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-Fix labels 2026-01-31 08:45:21 +00:00
Author
Owner

@DHowett commented on GitHub (Aug 23, 2025):

I'm sorry, this is not something we are going to do. Giving applications access to their own console window handles was a big enough mistake as it is.

If you want to coordinate with an application to manipulate its console session, you will need to do that coordination work yourself.

What is your use case?

@DHowett commented on GitHub (Aug 23, 2025): I'm sorry, this is not something we are going to do. Giving applications access to _their own_ console window handles was a big enough mistake as it is. If you want to coordinate with an application to manipulate its console session, you will need to do that coordination work yourself. What is your use case?
Author
Owner

@eabase commented on GitHub (Aug 23, 2025):

@DHowett

The use case is that I have about ~10 tabs open with various environments. (MSYS, Powershell, CMD, pwsh DEV, or Cygwin.) Every now and then something get messed up in one of the terminals and freezes the tab. It's nearly impossible to track down which process belongs to which tab, so I can kill the problem process, without losing the entire tab + it's history.

For example, using Nano (for windows) in powershell, and pasting in stuff copied from a web browser, often freezes the process. (Some UTF-8 character strings are misunderstood as terminal control characters..

Another example, is running a loop with sleep in powershell in one tab, then putting your computer to sleep, and awaken it, the sleepy tabs get frozen. CTRL-C or CTRL-\ or anything, doesn't work.

Here's screen shot, where I was lucky to find the process and killed it with pskill64. It just reloaded the pwsh profile/process seemingly without loss.

Image
@eabase commented on GitHub (Aug 23, 2025): @DHowett The use case is that I have about ~10 tabs open with various environments. (MSYS, Powershell, CMD, pwsh DEV, or Cygwin.) Every now and then something get messed up in one of the terminals and freezes the tab. It's nearly impossible to track down which process belongs to which tab, so I can kill the problem process, without losing the entire tab + it's history. For example, using Nano (for windows) in powershell, and pasting in stuff copied from a web browser, often freezes the process. (Some UTF-8 character strings are misunderstood as terminal control characters.. Another example, is running a loop with sleep in powershell in one tab, then putting your computer to sleep, and awaken it, the sleepy tabs get frozen. `CTRL-C` or `CTRL-\` or anything, doesn't work. Here's screen shot, where I was lucky to find the process and killed it with `pskill64`. It just reloaded the pwsh profile/process seemingly without loss. <img width="717" height="156" alt="Image" src="https://github.com/user-attachments/assets/c4d962af-2cd6-4402-b1f5-53aadf1e6215" />
Author
Owner

@DHowett commented on GitHub (Aug 26, 2025):

Some UTF-8 character strings are misunderstood as terminal control characters

That sounds like a very good bug to file on Nano!

For the rest, though... does this help?

Image

You can terminate any running--or hung--process in any terminal pane or tab and relaunch the session with this command. You can get at the command palette with Ctrl+Shift+P.

@DHowett commented on GitHub (Aug 26, 2025): > Some UTF-8 character strings are misunderstood as terminal control characters That sounds like a very good bug to file on Nano! For the rest, though... does this help? <img width="1740" height="918" alt="Image" src="https://github.com/user-attachments/assets/a04ef810-b8fe-439b-bb2e-ea32f9185eb2" /> You can terminate any running--or hung--process in any terminal pane or tab and relaunch the session with this command. You can get at the command palette with <kbd>Ctrl+Shift+P</kbd>.
Author
Owner

@eabase commented on GitHub (Aug 27, 2025):

Yes, That looks promising! Thank you.

@eabase commented on GitHub (Aug 27, 2025): Yes, That looks promising! Thank you.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#23541