DataSpell ↔ Jupyter Kernel: Handling Protocol 6.0 Compatibility

1. Implications of rejecting protocol 6.0 kernels

When DataSpell refuses to connect to a kernel that advertises protocol 6.0, the IDE simply aborts the handshake. Users cannot execute notebook cells, and any features that rely on new message types (e.g., custom, display_data upgrades) are unavailable. In practice:

• Cell execution stops at the first kernel‑initiated message that DataSpell does not understand.
• Interactive widgets or extensions that depend on protocol 6.0 features will fail silently or produce error logs.
• The user may be forced to downgrade the kernel or use an older DataSpell version that accepts legacy protocols.

2. Should DataSpell implement dynamic protocol negotiation?

Given that many kernels have migrated to 6.0, a graceful fallback would improve usability without forcing a full client rewrite. A pragmatic approach is:

1. During the initial handshake, read the protocol field from the kernel’s kernel.json.
2. If the value is >5.7.1, log a clear warning and offer the user an option to proceed with legacy handling.
3. When the user accepts, strip or ignore unsupported message types and map legacy messages to the nearest compatible ones.
4. Keep a separate code path for protocol 6.0 so that future major releases can drop the fallback without breaking existing users.

Implementing this does not require a full protocol 6.0 implementation and can be delivered in a minor update. It preserves backward compatibility while giving users a clear choice. The trade‑off is the added complexity of maintaining two code paths, but the benefit of not forcing users to downgrade kernels is significant.

3. Projected timeline for official support

JetBrains DataSpell typically follows a quarterly cadence for major/minor releases. The latest public information shows no explicit roadmap entry for protocol 6.0, but the following points help estimate a window:

• The Jupyter protocol 6.0 was finalized in early 2023.
• DataSpell’s last release (2026.2) still lists support up to 5.7.1.
• Feature upgrades of this nature are usually bundled with a new major/minor release rather than a patch.
• Given the 3–6 month window between releases, a plausible window for protocol 6.0 support is within the next 4–5 months from the current date (i.e., by the end of 2026‑Q4 or early 2027‑Q1).

Until a formal announcement, users should monitor the DataSpell issue tracker, release notes, and community forums for confirmation.

Practical verification steps

1. Run jupyter kernelspec list to inspect the kernel.json of your kernel and confirm the protocol field.
2. Open DataSpell and attempt to connect to the kernel. Note any compatibility warnings in the IDE console.
3. Check the DataSpell release notes (e.g., 2026.1, 2026.2) for mentions of “Jupyter protocol 6.0” or an updated client library.
4. Search the JetBrains GitHub repository for issues tagged protocol‑upgrade or jupyter‑protocol‑6 to see if a feature branch exists.

Missing diagnostic detail

To tailor the recommendation more precisely, could you tell me which DataSpell version you are currently using? This will help determine whether a fallback is already available or if a new release is required.