Copilot Agent run_in_terminal fails with ENOPRO: No file system provider found in GitHub Codespaces

[petersonjdNIH]

Fair warning, I had GitHub Copilot running Claude Sonnet 4.6 work through the most annoying GitHub Codespaces issue I've ever seen, and I think it's a bug with the web version of VS Code. A lot of this work was assisted by GitHub Copilot running Claude Sonnet 4.6, and I'll take any blame for this work not being sufficient.

I just don't know how to work around this issue. It seems to be totally stuck, so I used my limited ability to generate an easy to reproduce repo of the problem.

Summary

When GitHub Copilot Agent mode invokes its run_in_terminal tool inside a GitHub Codespace (VS Code Web), the call consistently fails with:

ENOPRO: No file system provider found for resource 'file:///workspaces/<repo-name>'

This crashes the Copilot Chat session — subsequent file system tool calls also fail, making the agent unresponsive until the browser tab is refreshed, at which point the cycle repeats.

The VS Code terminal works fine when the user types commands directly. Only Copilot Agent's programmatic run_in_terminal tool is affected.

Minimal reproducer

https://github.com/petersonjdNIH/vscode-enopro-repro

Open this repo in a Codespace in iOS or macOS Safari, open aCopilot Chat in Agent mode, and ask it to run any terminal command (e.g. `echo hello`) more than once.

Environment

Field	Value
Platform	GitHub Codespaces (VS Code Web, browser)
Devcontainer base image	mcr.microsoft.com/devcontainers/base:ubuntu-24.04
Reproducible across reloads	✅ Yes — window reload does not fix it
Reproducible across container rebuilds	✅ Yes — full rebuild does not fix it

Steps to reproduce

1. Open https://github.com/petersonjdNIH/vscode-enopro-repro in a Codespace on iOS or macOS Safari.
2. Wait for the container to fully start.
3. Open GitHub Copilot Chat → switch to Agent mode.
4. Send this prompt a few times: _"Run echo hello in the terminal".
5. Observe the tool call fail with the ENOPRO error.

Expected behaviour

Copilot Agent executes the command, receives the returned output, and responds to it.

Actual behaviour

ERROR while calling tool: ENOPRO: No file system provider found for resource 'file:///workspaces/vscode-enopro-repro'
Please check your input and try again.

The Codespace VFS provider appears to not be registered (or has been de-registered) for the workspace root by the time the Copilot tool makes its call.

Additional observations

• No custom extensions, tasks, or workspace settings — minimal devcontainer config only
• The error surfaces on the very first terminal tool call, not after some trigger
• Related closed issue: GitHub Issue: Terminal Connectivity Issues in VS Code Copilot #283806 (closed as not-reproducible, but issue persists as of March 2026)

Workaround

In Safari? None. Users must type all terminal commands manually; Copilot Agent cannot automate terminal operations in Codespaces. Or switch to the thick client on macOS.

[AgileJoshua]

Still experiencing this in codespaces via web in Safari OSX browser, works with Chrome on OSX. Version in the codespace says VSCode 1.113.0 , with the sample provided https://github.com/petersonjdNIH/vscode-enopro-repro, any terminal command by Copilot fails, user executed commands work without issue.

Software versions:
OSX: 26.3.1
Chrome: 146.0.7680.165
Safari: 26.3.1

[Sekkyo]

@meganrogge This seems to be reproducible in specific scenarios.

[AgileJoshua]

Additional testing suggests that terminal commands are being executed successfully - I can see the results of the execution in the chat. However copilot cannot pick it up. Logs from copilot in codespace environment below and screenshot of the terminal command's results shown in chat (screenshot is from a different session, so a different terminal command to the error logs). Below is from an iPad, same issues on OSX in Safari browser.

Screenshot of command being executed successfully

Terminal command runs, as shown in the terminal preview, but Copilot claiming the command failed.

---

2026-04-13 16:54:48.778 [warning] Error compiling input schema for tool run_in_terminal: Error: strict mode: unknown keyword: "enumDescriptions"
2026-04-13 16:54:53.662 [error] Error from tool run_in_terminal with args {"command": "find /workspaces/vscode-enopro-repro -type f -exec ls -lh {} \; | sort -k5 -hr | head -1", "explanation": "Find all files in the repo and display details sorted by size in descending order, showing the largest file first", "goal": "Identify and display details of the largest file", "mode": "sync", "timeout": 5000}: ENOPRO: No file system provider found for resource 'file:///workspaces/vscode-enopro-repro': withProvider@https://assets.github.dev/stable/41dd792b5e652393e7787322889ed5fdc58bd75b/out/vs/workbench/workbench.web.main.internal.js:4894:134701

---

From Agent Chat logs

---

Tool Call - call_1KU5ASk1asHwVoalPh0Gd9TK__vscode-1776099162477

Request

id   : call_1KU5ASk1asHwVoalPh0Gd9TK__vscode-1776099162477
tool : run_in_terminal
args : {
  "command": "set -e && cd /workspaces/vscode-enopro-repro && largest=$(find . -type f -printf '%s\	%p\
' | sort -nr | head -1 | cut -f2-) && ls -lh \"$largest\" && stat \"$largest\"",
  "explanation": "Find the largest file in the repository and print its file details from the terminal.",
  "goal": "Identify largest repo file",
  "mode": "sync",
  "timeout": 10000
}

Response

ERROR while calling tool: ENOPRO: No file system provider found for resource 'file:///workspaces/vscode-enopro-repro'
Please check your input and try again.

Thinking

thinkingId: bLAMJoX59diFqywEQkFpu4ujUaEofSQD09l2dM4EDzHdUS2sxq06+S5ldn1ercDxnhQPLE/xU4y3r/9OR+JkZzmSaL5tQI32sN75VJ7xN/lyOAIDbzjRbiu3wzw+egruzUXr+GdH786uPV9rFA6Mb/8U+5tlop0dTbGQRfsZQAJMhPB5nYLndLi98kOnKPOpwEf7iB0Q4Y8AcpqXALnR/1prP6cleQZO7BciSI15dpORVx1fyI1lLTguMycII5QqduKFDLMTm17MvlufcWB0fkxIY3D4+qu54BQjU1Vl5dUCo5GQLxtJqxAtJaSaJeiIFRqYL7Bli4lXyAaPW4CYQWcVsD1OETDlb9WnThepGvLP7D+MPzUC7m9qpIQW/r8zgx7N1k0275gfozF5oxhPRg==

---

Versions from "About" in the codespace

Version: 1.115.0
Commit: 41dd792
Date: 2026-04-07T22:04:57Z
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.4 Safari/605.1.15

[petersonjdNIH]

I'm able to reproduce this reliably now at the second run_in_terminal call. It pretty much makes VS Code in Safari with GitHub Codespaces unusable. I'm mostly using Codespaces in the VS Code thick client as a result. I suspect each of my team on macOS has hit this barrier too.