jupyter connect not finding kernels that other jupyter tools does on macos

[maxandersen]

Describe the bug

I use vsccode, cursor, jupyter itself, and various jupyter tui based tools and they all find the kernels I have installed in the common location: ~/Library/Jupyter/kernels/

But with "!jupyter connect" non of the kernels are found.

I have no conda installed. polyglot built in kernels works.

So where are the kernels being attempted loaded from woul be good to know.

Please complete the following:

Which version of .NET Interactive are you using? (In a notebook, run the #!about magic command. ):

.NET Interactive

© 2020-2025 Microsoft Corporation

Version: 1.0.632301+7d35ce3be7eb7a603527a3683b691d5e9922adca

Library version: 1.0.0-beta.25323.1+7d35ce3be7eb7a603527a3683b691d5e9922adca

https://github.com/dotnet/interactive

• OS
  • [ ] Windows 11
  • [ ] Windows 10
  • [x] macOS
  • [ ] Linux (Please specify distro)
  • [ ] iOS
  • [ ] Android
• Browser
  • [x] Chrome
  • [ ] Edge
  • [ ] Firefox
  • [ ] Safari
• Frontend
  • [ ] Jupyter Notebook
  • [ ] Jupyter Lab
  • [ ] nteract
  • [x] Visual Studio Code
  • [ ] Visual Studio Code Insiders
  • [ ] Visual Studio
  • [] Other (please specify)

Screenshots

If applicable, please add screenshots of the entire VS Code window.

[maxandersen]

note, I realized the docs at state https://github.com/dotnet/interactive/blob/main/docs/jupyter-in-polyglot-notebooks.md that a jupyter install needs to be available; I assumed polyglot notebook would be able to work with the jupyter installs vscode jupyter notebook support used. That seem NOT to be the case as when I explicitly installed jupyter in my PATH - "connect jupyter" now does "something" ...though it seems stuck.

So maybe my question is more - can't polyglot notebooks use the jupyter connection info vscode already has?

[varndellwagglebee]

having the same issue

[jonsequitur]

Could you provide some logs? You can enable logging by editing the Polyglot Notebooks extension's settings for Kernel Transport Args and adding the following:

"dotnet-interactive.kernelTransportArgs": [
    "{dotnet_path}",
    "tool",
    "run",
    "dotnet-interactive",
    "--",
    "[vscode]",
    "stdio",
    "--working-dir",
    "{working_dir}",
+   "--log-path",
+   "c:\\temp\\your-log-folder-name",
+   "--verbose",
],