VS Code users struggle to browse files on remote Jupyter servers
People using remote Jupyter kernels in VS Code can have trouble browsing files on the server from the editor, especially when its explorer shows a different filesystem. Some resort to cell magics and operating-system calls, which users describe as confusing compared with a dedicated file browser. They also want to open a remote workspace from a URI, and one user reports having to re-enter a server password in new windows.
For data scientists and ML developers using remote Jupyter kernels in VS Code. Mentioned from Jan 2020 to Jun 2023 on GitHub.
5 different people described this problem in 3 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 6.7/10
- Frequency
- 6.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
The current way of exploring remote files in VS Code is not very UI-friendly when connected to a remote kernel. Users would have to use cell magics through the os library, which isn't the best experience (and also confusing because the output (obviously) doesn't match what's shown on the VS Code file explorer)
Even if I'm storing my code locally I will probably have data on the remote that may need to be examined and having no direct way of doing that is a stopping point.
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 4 places to find your first customers
- 4 more quotes from people who have this problem
- Current workarounds, existing solutions and risks