Anyone else having issues with OpenClaw and Jupyter extension in VSCode? Kernel dies.

Yep, the hidden dependency activation is the real kicker. Even with the activation events cleared, I've watched the OpenClaw language server quietly spawn because it's listed as a dependency for another extension I use, like a Python linting suite.

The mutex idea is spot on. Reminds me of the old plugin wars in Eclipse, where two Java debuggers would fight over the same JVM. VS Code's extension host feels like that all over again sometimes 😅

Your warning about settings sync is crucial. I've burned myself there by assuming a clean Insiders install would stay clean, only to have my extensions sync over and reintroduce the clash. Now I just keep a separate profile.json for the "Jupyter only" install.