How to switch conda environments in the VS Code Copilot Chat terminal?

[mysilicons]

Select Topic Area

Question

Copilot Feature Area

VS Code

Body

When I use Copilot Chat in VS Code, it always uses the terminal to help me debug code. However, I'm puzzled that Copilot consistently invokes the default base environment, which is entirely different from my project's environment. How can I configure Copilot to automatically use my project's conda environment instead of repeatedly specifying it during conversations? Is there a specific setting to directly designate the conda environment Copilot should use each time? This is crucial for me.

[novello-dev]

Hey! I’ve actually bumped into this same issue before, so I get the confusion. It’s pretty weird when Copilot insists on using the base Conda environment even though the project is clearly using another one.

What usually fixes it for me is just setting the default terminal inside VS Code to the Conda environment I want. If you open the Command Palette and search for “Terminal: Select Default Profile”, your Conda env should be listed there. Pick it, close whatever terminal is open, and let VS Code start a new one. Copilot tends to just follow whatever VS Code thinks is the “main” terminal 🤷‍♂️.

Another thing worth checking is the auto-activation setting from the Python extension. Make sure VS Code is actually activating the environment automatically when a terminal opens. Otherwise Copilot pops in like “hello base environment” every single time haha.

And just in case, I usually set the interpreter for the workspace too (using “Python: Select Interpreter”). Sometimes Copilot behaves better when that’s set correctly, even if it shouldn’t technically matter.

Let me know if that works for you! And if it does, marking this as the answer would help other people running into the same thing.

That's such a cute kittie btw <3

[mysilicons]

Thanks for the suggestion, but I tried it and couldn't find my conda environment in the default terminal profile—probably because I'm on a remote server. Looks like there's no easy fix for this right now. I'll just stick to telling Copilot which conda environment to use at the start of our chats.

Thanks again for your help though!

[novello-dev]

Since you are on a remote server, the UI often fails to auto-detect the environments correctly, which is why the dropdown is missing. The cleanest fix that keeps your project isolated without messing up your global server configuration is to manually define a terminal profile in your workspace settings. You can open your remote .vscode/settings.json file and add a terminal.integrated.profiles.linux entry that points specifically to your conda environment path or runs the activation command. Once you set that specific profile as the default for the workspace, Copilot and new terminals will catch on immediately. It’s a bit more manual work than the local version but it’s bulletproof for SSH connections.

Let's hope this works! And if it does, marking this as the answer would help other people running into the same thing.

[novello-dev]

"Wait, looking at your screenshot, I see an entry named 'conda-AI' in the dropdown list, but your current selection is set to 'null'.

If 'conda-AI' corresponds to the environment you need, you might just need to select it right there! The 'null' setting forces VS Code to fall back to the generic system default (which explains why you keep getting the base env).

Try selecting 'conda-AI' and opening a new terminal. If that's the wrong environment, then we'll definitely need to use the JSON method to add the correct one manually." But that's the nuclear option. Hope you can get it right. There's also a possibility of the problem being something to do with Copilot.

[mysilicons]

conda-AI is a terminal profile I created manually. I’ve already tried setting it as the default terminal, but when Copilot opens a terminal to run commands, it still uses the base environment. I also configured settings.json in my project, but that only affects terminals I open myself. The terminals Copilot opens automatically still don’t switch to the project’s conda environment. I think this is a design issue with Copilot and will probably need to be fixed in a future update.
But thanks for your answer anyway.

[novello-dev]

No worries! Yeah… it really didn’t need to work this way.
If you have the time, I think it’s worth opening an issue on the Copilot GitHub, this looks like something they might want to fix.
Could help others running into the same thing too.