microsoft / microsoft/vscode-remote-release
remote-ssh throw exception in the latest v1.103 vscode
Open
Nobody has claimed this yet.
ssh
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Is there an existing issue for this bug?
- I have searched the existing open issues and found none that apply.
- If I find any issue of interest that is related or closed, I will included a link to it in this issue.
Required Troubleshooting Steps
- I have read and performed the troubleshooting steps
- I have tried both values of the
remote.SSH.useLocalServersetting - My issue was not covered in the Tips and Tricks linked from the Troubleshooting Wiki.
- I will include a complete copy of my Remote - SSH logs by running Remote-SSH: Show Log in the command palette or from View > Output in the menu bar
[Optional] Diagnose with Copilot
I did not ask the @remote-ssh participant for help
In step 2 of the troubleshooting wiki, what was the result of running the generated SSH command verbatim outside of VS Code?
I did not try step 2 of the troubleshooting steps
Remote-SSH Log
Remote-SSH Log
the remote-ssh log cannot see the error, the extension throws exception:
2025-08-14 13:38:51.614 [error] [Window] navigator is now a global in nodejs, please see https://aka.ms/vscode-extensions/navigator for additional info on this error.: PendingMigrationError: navigator is now a global in nodejs, please see https://aka.ms/vscode-extensions/navigator for additional info on this error.
at get (file:///c:/Program%20Files/Microsoft%20VS%20Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:388:6355)
at Object.<anonymous> (c:\Users\zhijiezhang\.vscode\extensions\ms-vscode-remote.remote-ssh-0.120.0\out\extension.js:2:486184)
at 19534 (c:\Users\zhijiezhang\.vscode\extensions\ms-vscode-remote.remote-ssh-0.120.0\out\extension.js:2:504894)
at r (c:\Users\zhijiezhang\.vscode\extensions\ms-vscode-remote.remote-ssh-0.120.0\out\extension.js:2:1108387)
at 92839 (c:\Users\zhijiezhang\.vscode\extensions\ms-vscode-remote.remote-ssh-0.120.0\out\extension.js:2:466959)
at r (c:\Users\zhijiezhang\.vscode\extensions\ms-vscode-remote.remote-ssh-0.120.0\out\extension.js:2:1108387)
at 49424 (c:\Users\zhijiezhang\.vscode\extensions\ms-vscode-remote.remote-ssh-0.120.0\out\extension.js:2:465816)
at r (c:\Users\zhijiezhang\.vscode\extensions\ms-vscode-remote.remote-ssh-0.120.0\out\extension.js:2:1108387)
at 17130 (c:\Users\zhijiezhang\.vscode\extensions\ms-vscode-remote.remote-ssh-0.120.0\out\extension.js:2:596135)
at r (c:\Users\zhijiezhang\.vscode\extensions\ms-vscode-remote.remote-ssh-0.120.0\out\extension.js:2:1108387)
at 87631 (c:\Users\zhijiezhang\.vscode\extensions\ms-vscode-remote.remote-ssh-0.120.0\out\extension.js:2:576866)
Expected Behavior
works normally without exception.
Actual Behavior
it throws exception, and some actions cannot be triggered.
Steps To Reproduce
- update to vscode 1.103 (1.101.,1.102.) has this problem, too
- update remote-ssh extension to current latest
- start vscode, and you'll see the error output from extension host.
Anything else?
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the exception with VS Code 1.103 and the current Remote-SSH extension, then inspect the stack trace in out/extension.js, especially the reported navigator access. Confirm the fix by verifying that the extension starts without the exception and that the previously blocked actions can be triggered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100