Jupyter notebook changes do not appear in the notebook editor or Git changes

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

1- jupyter notebook changes shown in json.
2- quick edits doesn’t highlight the notebook
3- git changes doesnt show up

Steps to Reproduce

When editing a Jupyter notebook in Cursor IDE, the changes are reflected only in the notebook’s raw JSON, not properly in the notebook interface. Quick edits also do not highlight or update the notebook correctly, and the modified notebook does not appear in Git/source control as changed.

Expected Behavior

1- jupyter notebook changes must be shown in notebook
2- quick edits must highlight the notebook
3- git changes must show up

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.0.12 (user setup)
VSCode Version: 1.105.1
Commit: a80ff7dfcaa45d7750f6e30be457261379c29b00
Date: 2026-04-04T00:13:18.452Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045

Does this stop you from using Cursor

Yes - Cursor is unusable

making changes in a notebook

Hey, thanks for the report and screenshots, they make it really clear.

I can see the issue. When you review the agent changes in a .ipynb file, the diff shows raw JSON instead of the normal notebook view. This is a known limitation. The notebook renderer isn’t supported yet in the Review diff/files tabs. All three items you mentioned, JSON instead of the notebook, no highlighting in quick edit, and Git changes, are related to this.

The team is aware. There’s no ETA yet, but your report helps us prioritize it.

Workaround: after the agent makes changes, switch to the bug.ipynb tab, not the Review tab, to see the result in the normal notebook view, and accept or reject changes from there.

It is not seen in there either

1 Like

I am experiencing the same actually, since version 2.4 or so, it used to work very well before.

the inline diffs are broken when the agent makes several changes in one notebook cell.

as an example, just now the agent made 3 changes in one cell for me
I see those edits in the chat itself but not in the open .ipynb

the only thing I see in ipynb is one of three inline diff edits with this message

the other 2 changes are PRESENT in the cell BUT the diffs are missing and not highlighted in the cell at all

@splitkeyboard do you know which version i can downgrade to so it works efficiently in notebooks?

Hey, it looks like your issue is different from the JSON rendering bug above.

If I’m understanding correctly, the agent makes several edits in the same cell, but the inline diff is only shown for one of them, and the rest are already applied without highlighting. So you can’t review or reject each change separately.

Can you share your exact Cursor version from Help > About, and a screen recording if you can reproduce it? I want to understand if this is auto-accept behavior or a diff display issue.

1 Like

Hey @vibe_jupyter, downgrading Cursor versions isn’t officially supported right now, unfortunately.

For now the workaround is the same: after the agent makes changes, switch to the actual .ipynb file tab, not via the Review panel. The team knows about the issue, and we’ll update the thread when there’s news.

@deanrie sure, here is:

1 Like

hi @deanrie! thanks for looking into this!
everything is like you said, indeed

the version is:

Version: 3.0.12
VSCode Version: 1.105.1
Commit: a80ff7dfcaa45d7750f6e30be457261379c29b00
Date: 2026-04-04T00:13:18.452Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.4.0

and the video

1 Like

PS:

recently noticed that an agent using gemini 3.1 pro preview doesn’t mention diffs/“patches” in the chat sometimes.
It does apply changes to the notebook but ignores mentioning these changes in the chat.

so with gemini 3.1 pro specifically – I don’t see any log of changes other than git diff.

Not 100% sure if the root-cause is the same or whether this bug is known, however, do let me know if you would like me to reproduce it and make a recording!