Explanation#
Understand why Conda Code behaves the way it does.
Regular environments and workspaces
One provider presents two environment sources while keeping their mutation rules intact.
Project files, lockfiles, and workspaces
Why project files create regular named environments while workspaces remain manifest-managed.
The provider model
How Conda Code uses the Python Environments API and why another conda branch can remain visible.
Ecosystem fit
How conda-workspaces, conda-pypi, conda-global, and Pixi Code relate to Conda Code, including which manifests contribute workspace tasks.