My project type was incorrectly identified.

[LuShengcan]

Version

• vscode about:
  版本: 1.108.0 (system setup)
  提交: 94e8ae2b28cb5cc932b86e1070569c4463565c37
  日期: 2026-01-08T13:53:10.781Z
  Electron: 39.2.7
  ElectronBuildId: 12953945
  Chromium: 142.0.7444.235
  Node.js: 22.21.1
  V8: 14.2.231.21-electron.0
  OS: Windows_NT x64 10.0.22621
• ms-python.vscode-python-envs: 1.16.0

---

Description

When I create and open a workpace, then i add three folders to the workpace. Two of the folders are python projects, and the third forder is vue3+electron project.

Out of vscode, I add the miniforge3/condabin to the path, and I create a conda environment.

Now, I open the workpace with three folders, then in Python Environments window, I find "Python Projects" folder has three items, but my vue3+electron is not python project, I select the conda environment create above for the two python projects, and leave the vue3+electron project not seted.

In the case above, when I config "python.terminal.activateEnvironment": true in user settings.json and config "python.terminal.activateEnvironment": false in my vue3+electron project/.vscode/settings.json, the config doesn't work, because when i right click the vue3+electron project and choose "open in Integrated Terminal", the terminal was opened and the conda env was auto activated, it's bad!!!

[anthonykim1]

I think there's multiple parts to this.

First, Wrong project detection non-Python project is being treated as a Python project? I'm not too sure about this @eleanorjboyd

Secondly, for activation, Do you just want your terminal to be not activated? or saying we activated wrong environment?
If it's the first set python-envs.terminal.autoActivationType to off

fyi We're planning to deprecate "python.terminal.activateEnvironment": setting so I just recommend you stick to python-envs.terminal.autoActivationType