Hey team! 
Just wanted to share some feedback and a small suggestion regarding the VSCode Mojo extension.
Right now, the default SDK version is set to 25.3, but it seems pretty unstable—I’ve been running into frequent errors, and it doesn’t seem to recover well once something goes wrong.
I tried manually switching to the nightly SDK that gets installed via pixi, and the difference was night and day—much more stable and smoother overall.
Since the magic CLI has been deprecated, it might be worth considering better native support for pixi in the extension. One idea: if the extension detects a .pixi/envs/default/share/max/modular.cfg file, it could maybe auto-add that SDK to the list—just to save users from doing it manually every time.
And if possible, a small update to the docs to reflect this would be super helpful for others trying to get set up.
3 Likes
I’m assuming this is with the Mojo VS Code extension and not the Mojo (nightly) one? I recommend trying with the Mojo (nightly) extension, that should pull the same Conda package as nightly Pixi use would. There have been some significant recent improvements in Mojo LSP performance and stability, and those will get picked up by the latest nightly Conda packages.
We’re currently planning out a significant rework of the VS Code extensions. Can’t promise a timeline on that, but I’d like to see us merge the two extension into one and place all of this in open source so that people can use it in other marketplaces and help extend its capabilities. Might take some work, but we’ll let you know as things progress there..
2 Likes
Oh, I hadn’t noticed there was a nightly extension! I’ve switched to it now, and that’s solved my problem – thanks for the heads-up!
I’m also really looking forward to the planned extension rework and the move to open source; that sounds like a great direction!