after vscode update, the langsmith can't make it

Does this issue occur when all extensions are disabled?: Yes/No

- VS Code Version:
Version: 1.132.0 (user setup)
Commit: df53daabb18cd157bdb08c7f01c34df936cf12f4
Date: 2026-08-04T15:30:20Z
Electron: 42.7.1
ElectronBuildId: 14760073
Chromium: 148.0.7778.280
Node.js: 24.18.0
V8: 14.8.178.38-electron.0
OS: Windows_NT x64 10.0.26200

- OS Version: local: window + remote: ubuntu

Steps to Reproduce
1.install the langraph langsimith
2.write something about the langgraph in python
3.run with langraph dev

show it on pc just like below:
(node:3385895) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
Unable to connect to VS Code server: Error in request.
Error: connect ENOENT /run/user/4100/vscode-ipc-239be9c1-8060-4725-a47f-ffaf7904d28a.sock
at PipeConnectWrap.afterConnect [as oncomplete] (node:net:1706:16) {
errno: -2,
code: 'ENOENT',
syscall: 'connect',
address: '/run/user/4100/vscode-ipc-239be9c1-8060-4725-a47f-ffaf7904d28a.sock'
}

Start by reproducing the report with the listed VS Code 1.132.0 setup on Windows with a remote Ubuntu window, then try `code --disable-extensions` and the Extension Bisect command. Compare the failure with the missing VS Code IPC socket and determine whether it is caused by VS Code's remote connection or the LangGraph/LangSmith extension; done means a confirmed cause and reproducible fix.

Written by the indexing model from the issue text.