Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

Persistent Jupyter kernel execution and live output streaming in VSCode

Details

External ID
49626144
Source
HN
Company
—
Product
Persistent Jupyter kernel execution and live output streaming in VSCode
Website domain
github.com
Launched
Sept. 9, 2026
Cohort
—
Upvotes
7
Upvotes percentile
0.4393939393939394
Tags
—
Fetched at
Sept. 13, 2026, 5:56 p.m.
Updated at
Sept. 13, 2026, 5:56 p.m.

Description

Hi HN, Every time I ran a training loop for a few days via Jupyter Notebook and ran into issues (network disconnected, my laptop suddenly died, etc.), I suffered from losing my ipykernel and cell outputs. I wanted to keep seeing my live outputs right inside the IDE without constantly checking W&B or log files. It is such a hassle. That's why I built Tithon. Let me know what you think!

Enrichment

Theme
utilities for Claude and Claude Code
Vertical
Horizontal
Function
Dev tools
Audience
Developer
AI stance
Not AI
Project type
Commercial product
Normalized one-liner
persistent jupyter kernel execution in vscode
Manually corrected
False

Could you build this?

Partial Interfacing with the VS Code extension API is straightforward, but maintaining persistent remote Jupyter kernel processes decoupled from IDE connection drops requires custom kernel management infrastructure.

What it would actually take: Requires a background daemon running on the remote host that proxies the ZeroMQ Jupyter kernel sockets and records message history (IOPub channels) into a durable buffer or database. A companion VS Code extension communicates with this daemon over WebSocket or SSH tunnel to replay missed cell outputs upon reconnection. Building the ZeroMQ proxy and session reconnection protocol requires deep networking and Jupyter protocol expertise.

Discussion

No comments on this launch.

Competitors

Other products that read as similar to this one — 34 launches clear the similarity bar, closest 8 shown.

Attention rank: #20 of 35 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 313 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a dev tools tool for Sales yet.