Introduction

Conda often activates the base environment automatically when a new shell starts. Some developers like that behavior, but many prefer a clean shell and only activate an environment when a project actually needs it. Conda supports that directly through a configuration setting.

Disable Automatic Base Activation

The usual command is:

conda config --set auto_activate_base false

This updates your Conda configuration so new shells stop activating base by default. It is the standard fix for users who want Conda installed but do not want every terminal session to start inside a Python environment.

Verify the Setting

After changing the configuration, confirm that Conda stored the value you expected.

conda config --show auto_activate_base

You should see output showing that auto_activate_base is set to false. If a shell is already open, start a new terminal session to verify the behavior change.

Conda stores configuration by scope, so the effective value may come from a user config file or a broader system config. If the behavior does not change, checking where the setting is defined is often more useful than rerunning the same command.

Understand What Changes in Daily Use

Disabling auto-activation does not disable Conda itself. It only means your prompt starts in the normal shell environment. When you want to work in Conda, activate an environment explicitly.

conda activate myenv

If you need the default environment for package management or troubleshooting, you can still activate it manually:

conda activate base

That keeps activation intentional instead of automatic.

Shell Initialization Still Matters

The setting above assumes Conda shell integration is already installed correctly. If conda commands are not available in a new shell, the problem is not base auto-activation. It is usually that the shell has not been initialized.

That is why auto_activate_base and conda init solve different problems. conda init wires Conda into the shell. auto_activate_base controls whether the base environment activates after that initialization runs.

When This Setting Is Useful

This configuration is especially helpful when:

• you use several Python tools and do not want base shadowing system commands,
• you prefer project-specific environments only,
• you want a simpler shell prompt,
• you work in scripts or automation where implicit environment activation is undesirable.

In those cases, disabling automatic base activation makes the shell state easier to reason about.

Reverse the Setting If Needed

If you later decide the old behavior was more convenient, you can turn it back on:

conda config --set auto_activate_base true

That restores the default startup experience for most Conda installations.

Common Pitfalls

• Expecting the current shell to change immediately without opening a new session.
• Confusing missing Conda shell initialization with base auto-activation behavior.
• Disabling auto-activation and then forgetting to activate a project environment manually.
• Editing shell startup files directly when the config setting already solves the problem.
• Assuming this setting removes access to conda commands rather than only changing startup activation.

Summary

• Use conda config --set auto_activate_base false to stop base from activating automatically.
• Verify the change with conda config --show auto_activate_base.
• Conda remains available; only the default startup activation changes.
• conda init and auto_activate_base are related but solve different problems.
• Manual activation keeps Python environments explicit and predictable.
• A clean default shell is often easier to reason about than an implicitly activated environment.