comfy-cli using the env before cloning

[greypage]

Describe the bug

I'm not sure if this counts as a bug, but this behavior is very strange.

I created an environment called comfyenv using conda and installed comfy-cli, which worked perfectly.

When I cloned comfyenv to comfyenv2 using conda, and then launched comfyUI using comfy-cli from comfyenv2, it was actually using the comfyenv environment.

I'm pretty sure I haven't messed up my environment, because when I execute Get-Command comfy | Select-Object Source in comfyen2, I get C:\Users\louis\anaconda3\envs\comfyenv2\Scripts\comfy.exe.

Then I execute comfy env.

(comfyenv2) PS C:\Users\louis> comfy env

Environment Information

┌──────────────────────────────────────┬─────────────────────────────────────────────────┐

│ 💻 Environment │ Value │

├──────────────────────────────────────┼─────────────────────────────────────────────────┤

│ Python Version │ 3.13.9 │

│ Python Executable │ C:\Users\louis\anaconda3\envs\COMFYENV\python.exe │
│ Virtualenv Path │ Not Used │
│ Conda Env │ comfyenv │
│ Config Path │ C:\Users\louis\AppData\Local\comfy-cli\config.ini │
│ Default ComfyUI workspace │ D:\comfy\ComfyUI │
│ Default ComfyUI launch extra options │ None │
│ Recent ComfyUI workspace │ D:\comfy\ComfyUI │
│ Tracking Analytics │ Enabled │
│ Background ComfyUI │ No │
│ Comfy Server Running │ No │
│ Current selected workspace │ → D:\comfy\ComfyUI │

└────────────────────────────────────┴────────────────────────────────────────────────┘

(comfyenv2) PS C:\Users\louis>

This doesn't seem right.

I then reinstalled comfy-cli in comfyenv2, and it worked perfectly, using the correct Python environment.
This doesn't seem right.

I then reinstalled comfy-cli in comfyenv2, and it worked perfectly, using the correct Python environment.

To Reproduce
create a new python env A
install comfy-cli
install comfyUI
clone env A to env B

Expected behavior
comfy-cli use right env where it is.

[dosubot]

Hi @greypage! I'm Dosu and I’m helping the comfy-cli team.

This is expected behavior when cloning conda environments that have installed CLI tools like comfy-cli. The reason is that the comfy-cli executable in the cloned environment may still reference the original environment's Python interpreter and environment variables, because the script's shebang and some environment variables (like CONDA_DEFAULT_ENV) can remain set to the original environment after cloning. comfy-cli determines the Python executable using sys.executable and the conda environment using CONDA_DEFAULT_ENV at runtime, so if these aren't updated, you'll see the old environment reported—even if the executable path looks correct. This isn't a bug in comfy-cli itself, but a side effect of how conda clones environments and how Python scripts are installed and referenced in Windows environments example.

Reinstalling comfy-cli in the cloned environment is the right fix, as it ensures the script references the correct Python interpreter and environment variables. If you ever see mismatches, check both the reported Python executable and CONDA_DEFAULT_ENV, and reinstall comfy-cli in the active environment if needed example.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}