-
Notifications
You must be signed in to change notification settings - Fork 37.3k
Description
Does this issue occur when all extensions are disabled?: YES
Version: 1.103.0 (Universal)
Commit: e3550cf
Date: 2025-08-06T21:40:10.271Z
Electron: 37.2.3
ElectronBuildId: 12035395
Chromium: 138.0.7204.100
Node.js: 22.17.0
V8: 13.8.500258-electron.0
OS: Darwin x64 24.6.0
Steps to Reproduce:
- Create workspace-specific terminal profile in
.vscode/settings.jsonthat loads.bash_profilewith shell functions and aliases which are specific to the project:
{
"terminal.integrated.defaultProfile.osx": "bash",
"terminal.integrated.profiles.osx": {
"bash": {
"path": "/usr/local/bin/bash",
"args": ["--rcfile", ".vscode/.bash_profile"],
"icon": "terminal-bash"
}
}
}It doesn't really matter what .vscode/.bash_profile contains. A simple alias will demonstrate the issue.
- Open a new integrated terminal window. The shell should be sourced with the contents of
.vscode/.bash_profile. This can also be verified:
$ ps auxw | grep '\b'$$'\b'
erhhung 19604 0.0 0.0 34884824 21348 s013 Ss 4:03PM 0:01.87 /usr/local/bin/bash --rcfile .vscode/.bash_profile-
Restart VSCode (or when prompted to restart for upgrade).
-
VSCode restores all previously opened windows, including workspace tabs and integrated terminal sessions. However, restored terminal sessions that were previously launched using a workspace-specific profile are no longer relaunched using that profile:
$ ps auxw | grep '\b'$$'\b'
erhhung 15265 1.7 0.0 35448024 22040 s009 Ss 3:50PM 0:03.20 /usr/local/bin/bash -lThe restored terminal session was instead launched using the global terminal profile, which lacks the additional shell functions and aliases needed for that workspace.