Remote developers lose access to long-running work after disconnects
Remote developers and notebook users can lose access to running tasks, kernel state, or output when an SSH connection, editor, or browser disconnects or restarts. Reconnection attempts may not restore the same session, leaving people unable to inspect progress or resume with their previous in-memory state. The reports describe workarounds, but not a reliable way to preserve and reattach to all of these sessions.
For remote developers and Jupyter users. Mentioned from Apr 2012 to Jun 2026 on GitHub.
11 different people described this problem in 9 separate discussions.
- Indie fit
- 6.0/10
- Pain
- 7.3/10
- Frequency
- 9.0/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- High
- Build difficulty
- High
What people said
Quoted word for word. Follow a link to read the whole discussion.
after some hours the connection gets disconnected and there is no way to see the progress or output of running cells
I just need to be able to reconnect the browser session to the kernel to get new outputs and to get at the data and code I've loaded. Kernel/Reconnect doesn't do it. I've also tried closing the tab and opening a new one from the Jupyter base page
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
- 10 more quotes from people who have this problem
- Current workarounds, existing solutions and risks