Provide controls to set them as active environment for your project, activate them in a terminal, and remove them[^1]
Temporarily[^2] modify an environment’s packages using the configured installer
[^1]: “remove” in this context means deleting it on disk, it will stay listed and will be recreated when interacting with it.
[^2]: since many actions currently use hatch run and therefore sync the environment, e.g. removing a package that is pulled in as a dependency will not persist for long.
Extension Settings
hatch.executable: path to the hatch executable (supports ~ expansion). Defaults to the output of which hatch.
Limitations
It’s pretty unclear which environments exist on disk and which don’t
We list internal envs that users don’t usually interact with, such as hatch-uv and hatch-build
