'notebook not found from uri'

[bdelabarreC]

Type: Bug

about a week ago github copilot chat stopped working.

The only error message it provides is 'notebook not found from uri:vs-code-notebook-cell:....'

No amount of searching through your help list has provided any solution for how to use github copilot with the most recent version of vscode.

I am going to dump my subscription to your service soon if this is not fixed.

Extension version: 0.26.3 VS Code version: Code 1.99.2 (4949701c880d4bdb949e3c0e6b400288da7f474b, 2025-04-10T01:21:25.295Z) OS version: Windows_NT x64 10.0.26100 Modes: Remote OS version: Linux x64 6.11.0-19-generic

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (12 x 2592)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	undefined
Memory (System)	15.91GB (4.38GB free)
Process Argv	--crash-reporter-id 604a7a9e-c192-46a2-83d1-7f24bb6a9433
Screen Reader	no
VM	0%

Item	Value
Remote	SSH: 192.168.86.33
OS	Linux x64 6.11.0-19-generic
CPUs	Intel(R) Core(TM) i9-14900KF (32 x 800)
Memory (System)	91.88GB (86.64GB free)
VM	0%

A/B Experiments

vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vscod805cf:30301675
binariesv615:30325510
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dwnewjupytercf:31046870
pythonrstrctxt:31112756
nativeloc2:31192216
5fd0e150:31155592
dwcopilot:31170013
6074i472:31201624
dwoutputs:31242946
customenabled:31248079
hdaa2157:31222309
copilot_t_ci:31222730
e5gg6876:31282496
cp15370_c:31280196
pythoneinst12cf:31262606
bgtreat:31268568
4gafe986:31271826
31787653:31262186
3e8i5726:31271747
996jf627:31283433
763bd867:31283000
747dc170:31275177
g20af354:31278749
aj953862:31281341

[FedericoCarotenuto]

Same for me. No output to whatever command I put in the chat, but if I click on "redo last request" it appears with the above mentioned error. Also the error points to an ipynb file that's not the current one.

[asif7adil]

Reporting the same issue. I tried updating the extension it did not work. Kindly resolve!

[xacantux-bot]

I have also been having the same issue since last week.

[scottrfrancis]

same here.

fwiw - I also use RunME Notebooks. Tried disabling that, but same result

[HinnyTsang]

Same issue when copilot keep try to read the ipython session that doesn't exist anymore. My quick fix is to open a new chat.

[kirar2004]

Same issue when copilot keep try to read the ipython session that doesn't exist anymore. My quick fix is to open a new chat.

Same issue here but the opening a new chat window worked

[bdelabarreC]

Opening a new chat as described does not work for me. I am still having the same issues (Notebook not found from uri:vscodenotebook-cell) despite installing all the latest updates as of April 18 2025.

My chat window was working up until roughly 2 weeks ago. I don't know if this come from VSCode or Github Copilot. Either way - it seems fixable (because it worked before....).

The only way I can access Copilot is via a right click to bring up a menu that has a CoPilot option an inline chat.

I prefer the chat window because I can compare the response to code I already have in my main window and decide whether to accept. The inline chat obscures this.

Github CoPilot folks - kindly fix this issue.

[olegperegudov]

Same here. After the last update. Please fix it.

[ch-ole]

I have the same issiue as descibed above. Copilot gives no response what so ever unless I click "redo last response". Then the error code shows up.

[DonJayamanne]

I'm sorry you are running into this issue, we have identified the cause of this and have a fix. Please can you try installing the latest pre-release version of the extension and VS Code insiders and confirm the issue has been resolved there.

[ch-ole]

I'm sorry you are running into this issue, we have identified the cause of this and have a fix. Please can you try installing the latest pre-release version of the extension and VS Code insiders and confirm the issue has been resolved there.

I tried doing that and initiated a new chat entirely. Seems to be working for now!

[DonJayamanne]

I believe this has been fixed, hence closing this issue for now If this persists, please ping here or feel free to create a new issue