Is there an existing issue for this?
OS/Web Information
Web Browser: Chrome
Local OS: Windows / macOS / Linux
Remote OS: Debian 13
Remote Architecture: amd64
code-server --version: 4.121.0
51bc3c0 with Code 1.121.0
Steps to Reproduce
Start code-server 4.121.0 on Debian 13.
Open a workspace in the browser.
Use GitHub Copilot / Copilot agent features that invoke terminal tools.
During or after terminal-tool invocation, the UI reports: ENOPRO: resource not found "file:///..."
Expected
When Copilot invokes terminal tools, code-server should not try to resolve inaccessible file:// resources in a way that breaks the UI. Any required resources should load correctly in the web/remote environment.
Actual
When Copilot invokes terminal tools, code-server sometimes tries to resolve a file:///... resource and fails with:
ENOPRO: resource not found "file:///..."
This appears to break or interfere with the Copilot terminal-tool flow in the browser.
Logs
服务端日志无明显异常，仅在界面层报 ENOPRO: 未找到资源 "file:///..."
Screenshot/Video
No response
Does this bug reproduce in native VS Code?
No, this works as expected in native VS Code
Does this bug reproduce in VS Code web?
No, this works as expected in VS Code web
Does this bug reproduce in GitHub Codespaces?
No, this works as expected in GitHub Codespaces
Are you accessing code-server over a secure context?
Notes
The main issue is not a missing CLI/config option by itself, but that in the code-server web environment, Copilot terminal-tool usage appears to trigger resolution of file:///... resources that are not available/servable there.
It would be helpful to know:
whether this is a known limitation in code-server + Copilot terminal integration,
whether those file:// resource accesses should instead use a web/remote-safe URI path,
and whether there is any workaround or patch available.
Is there an existing issue for this?
OS/Web Information
Web Browser: Chrome
Local OS: Windows / macOS / Linux
Remote OS: Debian 13
Remote Architecture: amd64
code-server --version: 4.121.0
51bc3c0 with Code 1.121.0
Steps to Reproduce
Start code-server 4.121.0 on Debian 13.
Open a workspace in the browser.
Use GitHub Copilot / Copilot agent features that invoke terminal tools.
During or after terminal-tool invocation, the UI reports: ENOPRO: resource not found "file:///..."
Expected
When Copilot invokes terminal tools, code-server should not try to resolve inaccessible file:// resources in a way that breaks the UI. Any required resources should load correctly in the web/remote environment.
Actual
When Copilot invokes terminal tools, code-server sometimes tries to resolve a file:///... resource and fails with:
ENOPRO: resource not found "file:///..."
This appears to break or interfere with the Copilot terminal-tool flow in the browser.
Logs
服务端日志无明显异常，仅在界面层报 ENOPRO: 未找到资源 "file:///..."Screenshot/Video
No response
Does this bug reproduce in native VS Code?
No, this works as expected in native VS Code
Does this bug reproduce in VS Code web?
No, this works as expected in VS Code web
Does this bug reproduce in GitHub Codespaces?
No, this works as expected in GitHub Codespaces
Are you accessing code-server over a secure context?
Notes
The main issue is not a missing CLI/config option by itself, but that in the code-server web environment, Copilot terminal-tool usage appears to trigger resolution of file:///... resources that are not available/servable there.
It would be helpful to know:
whether this is a known limitation in code-server + Copilot terminal integration,
whether those file:// resource accesses should instead use a web/remote-safe URI path,
and whether there is any workaround or patch available.