VSCode integration - need for official extension

[diegoferigo-rai]

Problem description

Hello everyone,

I'm opening this issue as a placeholder to consolidate discussions related to VS Code support.

Despite earlier efforts to streamline integration, the recent shift to the new Environment Managers has reintroduced a dependency on third-party extensions. The current documentation outlines the required setup steps, but the overall user experience remains suboptimal.

For broader industry adoption, a more robust and reliable solution is needed. Relying on community-maintained extensions is challenging, as they cannot always keep pace with upstream changes in VS Code or respond quickly to bugs or opened PRs.

Is there any plan to develop an official extension that provides full autodetection, as well as integrated run, debug, and pytest support? A seamless, officially maintained experience would significantly strengthen confidence in adopting Pixi across larger projects and ecosystems. Without it, there is a risk that teams may look toward alternative or custom solutions.

Thank you for considering this.

---

• Visual Studio Code with pixi not able to launch debugger #4323
• Support for pixi in VScode environments extension #4278
• Integration of pixi with vscode for C++ projects #1570
• Improve the Python experience on VSCode #2444
• Mention VS Code support in pixi docs #1787
• Support automatic recognition of pixi environments in IDEs: VS Code #411

---

• Extension support for environment managers microsoft/vscode-python-environments#79
• Change pixi activate way for vscode debugger renan-r-santos/pixi-code#21
• Recommend Pixi extension when Pixi environments are detected microsoft/vscode-python-environments#1252

[baszalmstra]

We currently don't have a plan to release an official extension but would definitely support a community effort!

[vigneshmanick]

To add additional information about the need for an official extension .

Generaly the end users computers are all domain joined (Active directory) and all the VSCode global settings are managed centrally via Group policy. This also includes the extensions that the users are allowed to use.

https://code.visualstudio.com/docs/enterprise/extensions#_allow-or-block-by-publisher

Though individual extensions can be white/blacklisted , admins / IT in general are more comfortable with whitelisting Organizations . e.g Astral, Github, Microsoft etc.

If pixi is already used in the company it means they have already whitelisted the organization so getting approval for official extension will be straightforward. The same cannot be said for community extensions.

Please consider having an official extension even if doesn't have all the features compared to community generated ones.

[baszalmstra]

Is there an extension we could maybe promote to the prefix-dev org?

[diegoferigo-rai]

but would definitely support a community effort!

Thanks @baszalmstra for the response. I understand the intention to support community driven solutions, but I believe this approach is part of the underlying issue rather than a viable answer.

Relying heavily on community maintained extensions introduces uncertainty around maintenance, responsiveness, and long term compatibility. As a concrete example, I opened a PR (renan-r-santos/pixi-code#40) two weeks ago and, despite follow ups, have not received any feedback. Situations like this make it difficult to depend on such tooling in a professional context.

At the moment, my pixi environment is not fully working in VSCode, and the only workaround would be to learn how to build and maintain a VSCode extension internally. That is a significant overhead and not something most teams can reasonably justify.

For broader industry adoption, especially in more controlled environments like those described above, there needs to be a stronger guarantee of maintenance and reliability. This is something that community efforts, by nature, cannot consistently provide.

Is there an extension we could maybe promote to the prefix-dev org?

https://github.com/renan-r-santos/pixi-code is a solid starting point. However, promoting it would ideally come with a commitment to active maintenance and responsiveness, so users can rely on it with confidence.

[skwde]

FYI, there is another "widely" (~12K atm) used extension available: https://github.com/jjjermiah/pixi-vscode.
This extension is also mentioned here: microsoft/vscode-python-environments#79

Note, the docs currently only mention https://github.com/renan-r-santos/pixi-code.

[diegoferigo-rai]

Thanks @skwde, that seemed quite a dead project since the last commit was from 2024. I just noticed it got a new commit a couple of days ago though. I'm not sure, however, if it supports the new Environment Managers setup from VSCode.