💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

I'm having the same issue when in VSCode in Codespaces when Copilot tries to run a terminal command (this happens in multiple unrelated Codespaces, started about 2 days ago).

2025-11-15 22:10:57.243 [error] Error from tool run_in_terminal with args {"command":"npm run dev","explanation":"Running the development server to check if the fixes resolved the issues.","isBackground":true}: ENOPRO: No file system provider found for resource 'file:///workspaces/ProductDevReact': mEt@https://assets.github.dev/stable/ac4cbdf48759c7d8c3eb91ffe6bb04316e263c57/out/vs/workbench/workbench.web.main.internal.js:8:153 j@https://assets.github.dev/stable/ac4cbdf48759c7d8c3eb91ffe6bb04316e263c57/out/vs/workbench/workbench.web.main.internal.js:3870:100465

Yeah,the issues still persistting.....

Can confirm, this issue still persists

Issue 1: Terminal Access Blocked

Cannot run pnpm test to verify tests pass
Error: ENOPRO: No file system provider found
Workaround: Manual verification documented for reviewer
Confidence: HIGH (95%) - Implementation logic matches test expectations exactly

I am also having this issue, just create a new code space and it has a terminal issue.

In case this is helpful.... (ignore if it is not)

I rolled back to Visual Studio v. 17.14.9 before the update where the bug was introduced and resolved these Copilot issues:

Key Reported Symptoms:
Context Blindness: The @workspace command and Agent mode fail to see any local files outside of the currently active document.

The Specific Error: Logs consistently show StreamJsonRpc.RemoteInvocationException: Authentication failed with Azure DevOps or Response status code does not indicate success: 401 (Unauthorized).

"File Not Found" UI Falsehoods: Even when files are clearly open, the UI may report "File Not Found" if the underlying search strategy fails to authenticate with the remote server.

Settings Persistence Failure: Like your experience, users have noted that attempts to re-authenticate or change settings often provide no relief, as the extension "eagerly" defaults back to the broken search strategy.

Rolling back to 17.14.9 is not a long term solution, but can help you in a pinch. I read this converstaion that said the fix should be in VS 2026 v 18.3. (https://developercommunity.visualstudio.com/t/Github-Copilot-Code-Search-stopped-worki/11005854)

Hope this helps someone.

still experiencing the same. this used to work before. seems it cant do anything on the terminal. xxx is my real project just masked it out.

Error Message: ERROR while calling tool: ENOPRO: No file system provider found for resource 'file:///xxx'

Error Code: ENOPRO (No Provider)

Context:

Tool: `run_in_terminal`
Workspace Path: xxx
Environment: Dev Container on Debian GNU/Linux 12 (bookworm)

can someone from the codespace or copilot team look into this? this is a deal breaker for me as a customer for paying for your products.