Jupyter users lose work when notebook sessions disconnect
Jupyter users running long computations, teaching with notebooks, or publishing interactive analyses report fragile state across editor restarts, connection interruptions, and exports. Kernels may stop or become unreachable, outputs produced while disconnected may be unavailable, and widget state can disappear from saved notebooks or HTML. The Joplin and Obsidian signals concern different note-taking workflows, so they are outside this core problem.
For jupyter users running long computations or sharing notebook outputs. Mentioned from Oct 2015 to Sep 2026 on product forums and GitHub.
10 different people described this problem in 6 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 6.4/10
- Frequency
- 8.6/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.6/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
For my use cases, model training can take days, even weeks, and what I have found is that I cannot leave this kind of notebook running and exit VS Code because otherwise the process dies immediately when I close the window
After a while if we go back into the notebook, the Notebook is unable to re-connect to the same kernel (kernel state is lost) * Similarly if user re-loads VS Code, the notebook is unable to re-connect to the same kernel (kernel state is lost)
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 5 places to find your first customers
- 8 more quotes from people who have this problem
- Current workarounds, existing solutions and risks