[BUG] Claude Code edits to Jupyter Notebook written to disk but do not automatically refresh in VS Code editor
Open 💬 23 comments Opened Dec 25, 2025 by JeremyDMoses
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
When Claude Code edits Jupyter notebook (.ipynb) files in VS Code, the changes are written to disk but do not automatically refresh in the VS Code notebook editor. Users must manually reload the file to see the changes.
What Should Happen?
When Claude Code edits a notebook file, VS Code should automatically detect the file change and refresh the notebook editor to display the updated content, similar to how it handles edits to regular text files (.py, .js, etc.).
Error Messages/Logs
Steps to Reproduce
- Open a Jupyter notebook (.ipynb) file in VS Code
- Ask Claude Code to edit cell content (code or markdown)
- Claude Code successfully makes the edit and writes to disk
- Observe that VS Code's notebook editor does not show the changes
- Manually reload the file using VS Code's "Reload from Disk" command
- Changes now appear in the editor
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.0.75 (Claude Code)
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
23 Comments
same here
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
This issue is still occuring on Claude Code version 2.1.37
I have the same issue as @JeremyDMoses where the changes are written to the disk but not refreshed in the notebook editor. I am using Claude Opus 4.6 and VSCode Version 1.109.2 on a Windows x64 OS.
Issue is still there on macos, Claude Code for VS Code 2.1.39
you can install the Notebook Hot Reload extension, it should fix
This is still occuring as of vscode v1.109.5 and claude code 2.1.56
still ocurring 1.109.5
I'm using an autoreload extension as work around
@alex2000ts 🙏
Thanks this worked for me!
still problem for me. will try the extension
still occuring 2.1.100
Still occurring with 2.1.121
@alex2000ts This worked for me, thanks. But everytime Claude makes changes, even though they now appear instantly on the Notebook, it still seems as if the editor thinks that I've just made an edit, and thus whenever I save or something I have to Click either "Revert" or "Overwrite" changes. What should you do there?
This is still an issue.
It's still an issue.
This is still an issue
This is still an issue!
Yes this is still an issue indeed. We would like to have notebook support for Claude Code please.
Still an issue
People, this isn't a Claude Code bug. In VSCode when a Claude Code agent modifies your text files regular text files (.py, .js, etc.), the changes appear immediately because the editor watches the filesystem and refreshes on changes. This "hot-reloading" isn't a feature implemented in most notebook editors (e.g. JupyterLab, Jupyter Notebook, VSCode's notebook editor) by default.
If you'd like VSCode to add it officially, this would be the relevant issue https://github.com/microsoft/vscode/issues/171920
In the meantime, if you want the hot-reload functionality in your VSCode Notebook editor so that changes made externally (such as via Claude Code) are reflected immediately in the editor, you may install an extension that implements this functionality. I've found two in the VSCode Marketplace, but make no guarantees regarding performance or security:
For JupyterLab and Jupyter Notebooks, installing the
jupyter-collaborationextension enables hot-reload.@evantkchong What you are describing here has nothing to do with the issue described here. You might want to read the first post again.
Still in issue. Using copilot for example works seamlessly. Should be same.
?? @limex is what I mentioned not pertinent to the issue?
Verbatim from the issue, emphasis mine:
I explained what the VSCode notebook editor does, and how to work around it. This isn't Claude Code's fault unless you're talking about their official VSCode extension, and even then I'm not sure this is the right place to raise a bug report about it.