A terminal that opens directly in Conda's base environment can hide which Python and package manager a command is using. Disabling auto activation keeps new shells in the system environment until an environment is activated deliberately.
Conda controls this startup behavior through the auto_activate configuration setting. The older auto_activate_base name is an alias, and default_activation_env remains base unless it has been changed.
The setting affects new shell sessions. If (base) is already active in the current terminal, deactivate it or open a new terminal after saving the setting; Conda can still activate base manually when it is needed.
Related: How to initialize Conda for a shell
Related: How to activate a Conda environment
$ conda config --show auto_activate auto_activate: True
True means Conda activates the configured default environment when the shell initializes. On most installations, that environment is base.
$ conda config --set auto_activate false
Older examples may use auto_activate_base for the same setting. Current Conda records the value under auto_activate.
$ conda config --show auto_activate auto_activate: False
(base) $ conda deactivate
Skip this step if the prompt does not show (base). The config change controls future shell startup; it does not remove the current active environment from an already-open terminal.
$ printf 'CONDA_DEFAULT_ENV=%s\n' "${CONDA_DEFAULT_ENV:-unset}"
CONDA_DEFAULT_ENV=unset
If the shell prompt hides environment names, the CONDA_DEFAULT_ENV check is more direct than looking for (base) in the prompt.
$ conda activate base
(base) $ printf 'CONDA_DEFAULT_ENV=%s\n' "$CONDA_DEFAULT_ENV" CONDA_DEFAULT_ENV=base