Pylance errors from chat virtual documents

[tj-aew]

Type: Bug

1. Do anything that makes Copilot register a virtual document for a Jupyter notebook with VS Code for the current session, for instance by attaching a Python Jupyter notebook to a Copilot chat by using # followed by the filename, or by having Copilot create it.

At this point, in our project, we get dozens of errors reported by Pylance/Pyright (mostly due to it not being able to find imports) whenever that Copilot session is open, and not when it isn't (even if we open the notebook itself), because when the session is open there's a virtual document for the Jupyter notebook registered with VS Code, which Pylance picks up, but then I guess because of the path of the virtual document, it can't find things at the root of our project it normally finds.

This is really problematic for our workflow, constantly warning us of errors that don't really exist.

Extension version: 0.48.1
VS Code version: Code 1.120.0 (0958016, 2026-05-12T20:17:22Z)
OS version: Windows_NT x64 10.0.26100
Modes:

[vs-code-engineering]

Thanks for creating this issue! It looks like you may be using an old version of VS Code; the latest stable release is 1.121.0. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

[tj-aew]

No difference with this:

Version: 1.121.0 (user setup)
Commit: f6cfa2ea2403534de03f069bdf160d06451ed282
Date: 2026-05-19T11:51:53+02:00
Electron: 39.8.8
ElectronBuildId: 13870025
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26100