Change:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.74.3 (Universal) OS Version: Darwin arm64 22.2.0 Steps to Reproduce: a terminal tab from the integrated terminal a process (e.g. node REPL) I started noticing recently that the terminal tab titles don't update with new processes anymore: ! The title on the right remains and not . This occurs in both zsh and bash terminals. My is set to . Changing it to adds the word correctly but doesn't update the process.
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.74.3. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
(I am using 1.74.3, bad copy paste)
I can replicate it. Here is my env info taken from the About VSCode modal: Version: 1.78.1 (Universal) Commit: Date: 2023-05-04T09:57:42.343Z Electron: 22.5.1 Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: Darwin arm64 21.5.0 Sandboxed: Yes
I face same probrem too. I tried uninstalling vscode and deleting , , then installed again. But the probrem still remains. And I tried changing , but it seems that "{sequence}" do not working. My environment . Laptop MacBookAir M2 2022 OS 13.3.122E261 VsCode Version: 1.78.2 Commit: Date: 2023-05-10T15:00:40.428Z (4 days ago) Electron: 22.5.2 Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: Darwin arm64 22.4.0 Sandboxed: No <img width="1015" alt=" 2023-05-15 10 19 42" src=""<img width="1019" alt=" 2023-05-15 10 20 08" src=""
Haven't looked into this but it could be related to
I have the same problem. MacBook Pro M1 2021 MacOS 12.6 VS Code info: Version: 1.78.2 (Universal) Commit: Date: 2023-05-10T14:44:45.204Z Electron: 22.5.2 Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: Darwin arm64 21.6.0 Sandboxed: Yes
I'm seeing the same thing after updating Version: 1.78.2 (Universal) Commit: Date: 2023-05-10T14:44:45.204Z Electron: 22.5.2 Chromium: 108.0.5359.215 16.17.1 V8: 10.8.168.25-electron.0 OS: Darwin arm64 21.6.0 Sandboxed: Yes
ptyProcess.process is always returning pwsh for me now here: <img width="1331" alt="Screenshot 2023-05-24 at 3 09 01 pm" src="" pretty sure this was caused by , previously it would not just return the process path for the shell but switch to inner shells.
Yeah switching to only retrieves info about the target PID, in this case the top level shell that got forked. If we want info on the current running process in the group then we would need to switch back to using . Originally, I switched this because of an issue with the control terminal being not correctly assigned leading to the API always returning the default root process which should now be addressed with , let me see if I am able to revert the change.
Update: reverting the above commit didn't resolve the issue, I will need to debug this a bit more.
Possibly related / similar sounding recent issue on Stack Overflow:
Reverting the node-pty update as it caused tests to fail:
I've been trying to programmatically set the title of a bash terminal without success, and glad that I chanced upon this issue. Here is the repro: System: Windows 11. Git Bash installed. VSCode version: 1.82.0 VSCode Workspace Settings: ! .bashrc The title of the bash terminal window remains stubbornly unchanged as . I'm assuming this issue will fix my use case. Thanks
that is indeed a bug, but it's separate to this one as this is macOS only. Created to track that.
are there any more details on this? Is there a way to fix the tests for that PR?
Looks like it's fixed now! !
It's working!! Thank you!!! !
/fixedWith interesting observation there were no functional changes between in node-pty, however the test failures were not encountered this time
Still doesn't work for me on 1.84.1 ! Does it require a specific ? I have set.
Isn't it working as intended then?
Sorry I'm not sure I follow; I'm trying to get the same behaviors as others are getting in this thread, e.g. showing or if that's the running process. It still isn't working for me so I'm wondering if my setting is off, but it seems to be the default value when I do "Reset setting".
is correct (to see etc.), so yes it looks like the fix hasn't worked for you

Discussion:
"native-is-elevated": "0.7.0", "native-keymap": "^3.3.2", "native-watchdog": "^1.4.1", <del> "node-pty": "1.1.0-beta1", </del> <ins> "node-pty": "1.1.0-beta3", </ins> "tas-client-umd": "0.1.8", "v8-inspect-profiler": "^0.1.0", "vscode-oniguruma": "1.7.0",

"keytar": "7.9.0", "minimist": "^1.2.6", "native-watchdog": "^1.4.1", <del> "node-pty": "1.1.0-beta1", </del> <ins> "node-pty": "1.1.0-beta3", </ins> "tas-client-umd": "0.1.8", "vscode-oniguruma": "1.7.0", "vscode-regexpp": "^3.1.0",

resolved "https://registry.yarnpkg.com/node-gyp-build/-/node-gyp-build-4.3.0.tgz#9f256b03e5826150be39c764bf51e993946d71a3" integrity sha512-iWjXZvmboq0ja1pUGULQBexmxq8CV4xBhX7VDOTbL7ZR4FOowwY/VOtRxBN/yKxmdGoIp4j5ysNT4u3S2pDQ3Q== <del> node-pty@1.1.0-beta1: version "1.1.0-beta1" resolved "https://registry.yarnpkg.com/node-pty/-/node-pty-1.1.0-beta1.tgz#95d4baf406c043b78042f951b325e9713df2beac" integrity sha512-h+1E/gX/brFqsp3yZKGERHOhdo1POG1rrsI+8tEuocqdEddHd029471gq8KOuiHKicd52h2pSU8Gtqb3Vo2PfQ== </del> <ins> node-pty@1.1.0-beta3: version "1.1.0-beta3" resolved "https://registry.yarnpkg.com/node-pty/-/node-pty-1.1.0-beta3.tgz#c750621a4effddd499fcbd15a2cf7679bee7b60f" integrity sha512-/QnWzklx8QcPcUUTWZSlY/YIz2IXo61KKx7O1H7aZ1YtMvmU1EFS/+hppmUSWV7+9WRCfAdov4K22u8knZ+IzA== </ins> dependencies: nan "^2.17.0"