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

Tab title not updating after closing ssh connection #15151

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

Originally created by @MrEmanuel on GitHub (Sep 9, 2021).

Windows Terminal version (or Windows build number)

1.9.1942.0

Other Software

WSL 2
OpenSSH_8.2p1 Ubuntu-4ubuntu0.1, OpenSSL 1.1.1f 31 Mar 2020

Steps to reproduce

  1. Open a new tab or instance of windows terminal. Notice the tab says "Ubuntu" (I'm using Ubuntu with WSL2)
  2. ssh to a remote machine
    ssh my_user@machine_ip_address
  3. Notice the tab title updates to "my_user@machine_ip_address"
  4. Exit ssh
    ctrl-d
  5. Notice the tab title is still displaying the remote machine address. "my_user@machine_ip_address"

Expected Behavior

Expected behavior is that the tab title should update when closing an ssh tunnel to a remote machine.

Actual Behavior

The tab title stays locked as the remote machine address, i.e my_user@machine_ip_address.

Originally created by @MrEmanuel on GitHub (Sep 9, 2021). ### Windows Terminal version (or Windows build number) 1.9.1942.0 ### Other Software WSL 2 OpenSSH_8.2p1 Ubuntu-4ubuntu0.1, OpenSSL 1.1.1f 31 Mar 2020 ### Steps to reproduce 1. Open a new tab or instance of windows terminal. Notice the tab says "Ubuntu" (I'm using Ubuntu with WSL2) 2. ssh to a remote machine `ssh my_user@machine_ip_address` 3. Notice the tab title updates to "my_user@machine_ip_address" 4. Exit ssh `ctrl-d` 5. Notice the tab title is still displaying the remote machine address. "my_user@machine_ip_address" ### Expected Behavior Expected behavior is that the tab title should update when closing an ssh tunnel to a remote machine. ### Actual Behavior The tab title stays locked as the remote machine address, i.e `my_user@machine_ip_address`.
claunia commented 2026-01-31 04:29:57 +00:00
Author
Owner
Copy Link

@MrEmanuel commented on GitHub (Sep 9, 2021):

I almost had a heart attack after (correctly) removing a database on my local machine and looking at the Windows Terminal tab (erroneously) telling me I'm still ssh'ed in to the production machine.

@MrEmanuel commented on GitHub (Sep 9, 2021): I almost had a heart attack after (correctly) removing a database on my local machine and looking at the Windows Terminal tab (erroneously) telling me I'm still ssh'ed in to the production machine.
claunia commented 2026-01-31 04:29:57 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 9, 2021):

Open a new tab or instance of windows terminal. Notice the tab says "Ubuntu" (I'm using Ubuntu with WSL2)

That would seem to suggest that your local shell in WSL isn't configured to set the tab title. What shell are you using in WSL locally? bash, zsh, fish?

I know in the stock .bashrc, there's the following snippet to set the tab title:

# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
    PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
    ;;
*)
    ;;
esac

So if you've modified your PS1 at all, that might not be present anymore.

@zadjii-msft commented on GitHub (Sep 9, 2021): > Open a new tab or instance of windows terminal. Notice the tab says "Ubuntu" (I'm using Ubuntu with WSL2) That would seem to suggest that your local shell in WSL isn't configured to set the tab title. What shell are you using in WSL locally? `bash`, `zsh`, `fish`? I know in the stock `.bashrc`, there's the following snippet to set the tab title: ```bash # If this is an xterm set the title to user@host:dir case "$TERM" in xterm*|rxvt*) PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1" ;; *) ;; esac ``` So if you've modified your PS1 at all, that might not be present anymore.
claunia commented 2026-01-31 04:29:57 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 13, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Sep 13, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
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 Needs-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity
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#15151
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?