Almost every conda command moves a package along one line: from a channel on the internet, into your local package cache, linked into an environment, and put on PATH by your shell. Learn that line once and the flags stop being arbitrary.
Distilled & cross-checked against: docs.conda.io (official cheatsheet + concepts) · conda-forge.org · anaconda.com/docs · github.com/conda-forge/miniforge · conda.org (CEP-29 MatchSpec) · bioconda · readthedocs conda guide. Verified 2026-08-26 against conda 26.7.0.
conda infoconda init bashconda activate into your shell rc. Also zsh, fish, powershell. Restart the shell after.conda update -n base condabase — nothing else should.conda config --set auto_activate_base falsebase in every new terminal.conda COMMAND --helpconda create -n myenv python=3.12conda create -n myenv python=3.12 numpy pandasconda create -p ./.venv python=3.12-p puts the env in a project folder instead of the shared envs dir.conda create --clone myenv -n myenv-expconda rename -n old newconda remove -n myenv --allconda activate myenvbin/ to PATH. Prompt shows (myenv).★conda deactivatebase.conda env list* marks the active one. Same as conda info --envs.★conda run -n myenv python app.pyconda env config vars set KEY=val -n myenvconda install numpy pandasconda install -c conda-forge polarsconda install conda-forge::polarsconda install -n myenv scipyconda install scipy --yesconda install scipy --dry-runconda install ./pkg.condaconda install numpy=1.26= means 1.26.* — any patch.★conda install numpy==1.26.4== pins that release precisely.conda install "numpy>=1.24,<2"< > * |.★conda install "numpy=1.24|1.26"conda install "pytorch=2.*=cuda*"conda install "pkg[version='>=1.2',build=py311*]"conda listconda list --show-channel-urlsconda list ^scikitconda search polarsconda search polars --infoconda repoquery depends scipyconda repoquery whoneeds numpyconda update numpyconda install numpyconda update --allconda remove numpyconda uninstall is an alias.conda remove -n myenv numpyconda config --show-sourcesconda config --add channels conda-forge--append puts it last instead.conda config --set channel_priority strictconda config --show channel_priorityconda install -c conda-forge --override-channels pkgconda config --remove channels defaultsdefaults + conda-forge is the classic breakage.conda env export --from-history > environment.ymlconda env export > environment.ymlconda list --explicit > spec.txtconda export --format=environment-yamlenvironment-json, explicit, requirements.conda export --file=environment.yamlconda env create -f environment.ymlconda env create -f environment.yml -n otherconda create -n myenv --file spec.txt--file also accepts environment.yaml and requirements.txt.conda env update -f environment.yml --prune--prune drops what's no longer listed.★conda compare environment.ymlconda install pippip isn't the base/system one.python -m pip install some-pypi-only-pkgconda install anything # after pipconda list --show-channel-urlspypi — that's your audit.conda list --revisionsgit log.★conda install --revision 3conda doctorconda doctor --fix--fix added in conda 26.1.★conda clean --index-cacheconda clean --all --dry-runconda clean --allconda clean --tarballsconda info --envs --size--size (conda 26.1) also works on conda env list and conda list.★conda config --set solver libmambaconda config --show solver.mamba install pkg.condarc. micromamba is a single static binary — ideal for CI.-n myenv--name. Lives in the shared envs dir; shows up in conda env list.-p ./.venv--prefix. Any path. Project-local, ships with the repo, but not listed by name.(omitted)base. Check your prompt first.conda config --set env_prompt '({name})'-p envs instead of printing the whole path.Not more commands — the models underneath them.
conda install really doesA solve is not a download. Conda reads your channel list in priority order, fetches each channel's index, and only then goes shopping — recursively, for every dependency.
strict vs flexible vs disabledThe single biggest source of broken conda environments. Suppose conda-forge sits above defaults, and both ship some-pkg — conda-forge at 1.0, defaults at 1.2.
Three optional fields hang off the package name. Getting = vs == wrong is the most common pinning bug in a shared environment.yml.
Conda tracks what conda installed. It cannot see pip's files — so pip goes last, or not at all.
environment.ymlThe file you should commit. Channel order is priority order, and the pip: block must come last.
Create: conda env create -f environment.yml
Sync: conda env update -f environment.yml --prune
conda is the tool — these are the ways to get itThey all give you the same conda command. They differ in what's preinstalled and which channel is wired in by default.
=1.26 → 1.26.*); two is exactupdate stays inside the major version; install takes the newestenv export pins builds to your OS< > * | before conda ever sees theminstall --revision N