Agent cannot access files within folder when using remote ssh
- Dominant language
- TypeScript
- Stars
- 193k
- Forks
- 42.4k
- PR merge metrics
- PR metrics pending
Description
Type: Bug
Reverting to version 1.133 fixes this.
Opening a previous folder located on a remote ssh nfs system. The agent is not able to access previously generated files and thus asks for permission citing " links to , which is outside the current folder" When hovering above the local path is shown, when hovering above the links to the full nfs path is shown. e.g. doc/AGENT_ONBOARDING.md vs /nfs/my/path/to/my/folder/docs/AGENT_ONBOARDING.md.
The agent or stack cannot tell that these are the same thing, even though the folder opened was specified as /nfs/my/path/to/my/folder
VS Code version: Code 1.137.0 (645f29cc3176500b4b5762ba887cf2a7f0ffdf2c, 2026-09-08T13:43:59-07:00)
OS version: Windows_NT x64 10.0.26200
Modes:
Remote OS version: Linux x64 5.14.21-150400.24.158-default
Extensions (8)
Name|Identifier|Author|Version
---|---|---|---
Jupyter Keymap|ms-toolsai.jupyter-keymap|ms-toolsai|1.1.2
Dev Containers|ms-vscode-remote.remote-containers|ms-vscode-remote|0.469.0
Remote - SSH|ms-vscode-remote.remote-ssh|ms-vscode-remote|0.124.0
Remote - SSH: Editing Configuration Files|ms-vscode-remote.remote-ssh-edit|ms-vscode-remote|0.87.0
WSL|ms-vscode-remote.remote-wsl|ms-vscode-remote|0.104.3
Remote Development|ms-vscode-remote.vscode-remote-extensionpack|ms-vscode-remote|0.26.0
Remote Explorer|ms-vscode.remote-explorer|ms-vscode|0.5.0
Remote - Tunnels|ms-vscode.remote-server|ms-vscode|1.5.3
Contributor guide
Assessment
This issue has not been assessed yet.