# \[Edited\] cannot debug mojo in vscode with pixi or pip (cli option deprecated) **URL:** \ **Category:** LSP\ **Tags:** discussion, vscode-extension\ **Created:** [January 5, 2026, 8:43pm UTC](https://forum.modular.com/t/edited-cannot-debug-mojo-in-vscode-with-pixi-or-pip-cli-option-deprecated/2577 "2026-01-05T20:43:47Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![batman](https://avatars.discourse-cdn.com/v4/letter/b/9fc29f/32.png) [@batman](https://forum.modular.com/u/batman)\ **Post date:** [January 5, 2026, 8:43pm UTC](https://forum.modular.com/t/edited-cannot-debug-mojo-in-vscode-with-pixi-or-pip-cli-option-deprecated/2577/1 "2026-01-05T20:43:47Z")
I was trying to install CLI so that I can debug mojo with vscode, but I ran into this error ```auto $ brew install modular ✔︎ JSON API cask.jws.json Downloaded 15.3MB/ 15.3MB ✔︎ JSON API formula.jws.json Downloaded 32.0MB/ 32.0MB ==> Fetching downloads for: modular ✔︎ Bottle Manifest ca-certificates (2025-12-02) Downloaded 2.0KB/ 2.0KB ✔︎ Bottle ca-certificates (2025-12-02) Downloaded 131.8KB/131.8KB ✔︎ Bottle Manifest readline (8.3.3) Downloaded 10.0KB/ 10.0KB ✔︎ Bottle readline (8.3.3) Downloaded 758.1KB/758.1KB ✔︎ Bottle Manifest sqlite (3.51.1) Downloaded 11.4KB/ 11.4KB ✔︎ Bottle sqlite (3.51.1) Downloaded 2.4MB/ 2.4MB ✔︎ Bottle Manifest xz (5.8.2) Downloaded 11.8KB/ 11.8KB ✔︎ Bottle xz (5.8.2) Downloaded 764.9KB/764.9KB ✘ Formula modular (0.9.3) Error: Failed to download resource "modular (0.9.3)" Download failed: https://dl.modular.com/public/installer/raw/names/modular-mac-arm64/versions/latest/modular-v0.9.3-macos-arm64.tar.gz ``` ---
**Author:** ![Ehsan](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.modular.com/ehsan/32/142_2.png) [@Ehsan](https://forum.modular.com/u/Ehsan)\ **Post date:** [January 5, 2026, 11:50pm UTC](https://forum.modular.com/t/edited-cannot-debug-mojo-in-vscode-with-pixi-or-pip-cli-option-deprecated/2577/2 "2026-01-05T23:50:02Z")
`modular` CLI has been deprecated! Wondering where did you find such instructions? Please see the [getting started](https://docs.modular.com/max/get-started) page. ---
**Author:** ![batman](https://avatars.discourse-cdn.com/v4/letter/b/9fc29f/32.png) [@batman](https://forum.modular.com/u/batman)\ **Post date:** [January 6, 2026, 5:20am UTC](https://forum.modular.com/t/edited-cannot-debug-mojo-in-vscode-with-pixi-or-pip-cli-option-deprecated/2577/3 "2026-01-06T05:20:08Z")
Here’s what I tried: `python3 -m pip install modular` then when I try to debug a mojo file, I get: > [“ERROR” - 9:18:37 PM] Cannot launch debug session with mojoFile specified (was ‘/Users/ksingh1/code/jedi/src/main.mojo’) because MAX was installed as a wheel. and > Debugging a Mojo file using the ‘mojoFile’ option is not supported when the Mojo SDK is installed as a wheel. I think Gemini suggested that I try install CLI, so I did `brew install` which is no longer valid option as you say ---
**Author:** ![melodyogonna](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.modular.com/melodyogonna/32/33_2.png) [@melodyogonna](https://forum.modular.com/u/melodyogonna)\ **Post date:** [January 6, 2026, 9:56am UTC](https://forum.modular.com/t/edited-cannot-debug-mojo-in-vscode-with-pixi-or-pip-cli-option-deprecated/2577/4 "2026-01-06T09:56:27Z")
Try using the Pixi option in the `getting started` page. ---
**Author:** ![batman](https://avatars.discourse-cdn.com/v4/letter/b/9fc29f/32.png) [@batman](https://forum.modular.com/u/batman)\ **Post date:** [January 6, 2026, 7:46pm UTC](https://forum.modular.com/t/edited-cannot-debug-mojo-in-vscode-with-pixi-or-pip-cli-option-deprecated/2577/5 "2026-01-06T19:46:50Z")
Opened the project using pixi shell. Still getting > [“ERROR” - 11:45:25 AM] Cannot launch debug session with mojoFile specified (was ‘/Users/ksingh1/code/jedi/src/main.mojo’) because MAX was installed as a wheel. my toml ```auto [workspace] authors = ["Kanwaljit Singh <>"] channels = ["https://conda.modular.com/max-nightly", "conda-forge"] name = "jedi" platforms = ["osx-arm64"] version = "1.0.0" [tasks] [dependencies] mojo = ">=0.26.1.0.dev2026010605,<0.27" ``` ---
**Author:** ![batman](https://avatars.discourse-cdn.com/v4/letter/b/9fc29f/32.png) [@batman](https://forum.modular.com/u/batman)\ **Post date:** [January 6, 2026, 7:49pm UTC](https://forum.modular.com/t/edited-cannot-debug-mojo-in-vscode-with-pixi-or-pip-cli-option-deprecated/2577/6 "2026-01-06T19:49:52Z")
With vscode open, I did ```auto (jedi) [ksingh1@IB-F25914YXHC] : jedi $ pixi clean removed /Users/ksingh1/code/jedi/.pixi/envs (jedi) [ksingh1@IB-F25914YXHC] : jedi $ pixi install ✔ The default environment has been installed. ``` here is the extension info ```auto Identifier: modular-mojotools.vscode-mojo Version: 26.0.3 Last Updated: 1 day ago Size: 4.00MB ``` ---
**Author:** ![batman](https://avatars.discourse-cdn.com/v4/letter/b/9fc29f/32.png) [@batman](https://forum.modular.com/u/batman)\ **Post date:** [January 7, 2026, 6:39am UTC](https://forum.modular.com/t/edited-cannot-debug-mojo-in-vscode-with-pixi-or-pip-cli-option-deprecated/2577/7 "2026-01-07T06:39:05Z")
Finally this mode worked! > $ mojo debug --vscode main.mojo but ya if I choose `Mojo: Debug` from vscode itself, it still says this is wheel