`comfy launch --background` fails with FileNotFoundError when comfy-cli is invoked by path

Abierto Apto para principiantes
  • ¿Algo no está bien?
#691 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@RaphaelFakhri ya está trabajando en esto.

Desde el 2/10/2026.

  • #963 de @RaphaelFakhri — abierto
  • #1058 de @perfectmodelslab — abierto

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
78/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Tranquilo
Stack tecnológico
python
Área
cli

Línea de trabajo

Comienza en comfy_cli/command/launch.py, en background_launch(), e inspecciona cómo se construye y se inicia el comando que se pasa a subprocess.Popen. Vuelve a ejecutar la reproducción del virtualenv con comfy ausente de PATH y verifica después que la misma CLI invocada mediante la ruta pueda iniciarse en segundo plano sin un FileNotFoundError y que el Workspace se ejecute.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug

Describe the bug
background_launch() re-execs the CLI as a bare "comfy" through subprocess.Popen (no shell=True), so the child is resolved via PATH. When comfy-cli is invoked by its own path from a virtualenv that hasn't been activated — e.g. /path/to/.venv/bin/comfy launch --background — the child spawn raises FileNotFoundError and the launch dies with an unhandled traceback.

This is a normal way to use a Python console script (it's how a script or launcher invokes a tool it installed into a project-local venv), and comfy-cli otherwise anchors subprocesses properly — resolve_python.py and uv.py use sys.executable throughout. Only this call site assumes PATH.

To Reproduce

python3 -m venv .venv-comfy
.venv-comfy/bin/pip install comfy-cli

# a stand-in workspace is enough to reach the failing call
mkdir -p fake-ws && echo 'print("hi")' > fake-ws/main.py

# the key condition: `comfy` is NOT on PATH
env -i HOME="$HOME" PATH=/usr/bin:/bin \
  ./.venv-comfy/bin/comfy --skip-prompt --workspace="$PWD/fake-ws" launch --background

Environment

  • comfy-cli 1.15.0
  • Python 3.11, Linux (originally hit on macOS / Apple silicon)
  • comfy-cli installed into a project-local venv and invoked without activating it

Observed

FileNotFoundError: [Errno 2] No such file or directory: 'comfy'

…raised from comfy_cli/command/launch.py → background_launch → subprocess.Popen.

Expected behavior
The background launch should start, as it does when the same binary's directory happens to be on PATH. Re-running the identical command with only PATH="$PWD/.venv-comfy/bin:$PATH" changed gets past the spawn and executes the workspace — PATH is the only variable.

Cause

comfy_cli/command/launch.py, in background_launch():

cmd = [
    "comfy",
    f"--workspace={os.path.abspath(os.getcwd())}",
    "launch",
]
...
process = subprocess.Popen(
    cmd,
    stdout=logfh,
    stderr=subprocess.STDOUT,
    env=env,
)

cmd[0] is a bare name, so Popen resolves it against PATH — which need not contain the comfy-cli that is currently running.

Suggested fix

Anchor the re-exec to the running installation rather than to PATH. Either of these is a no-op when comfy is on PATH:

cmd = [sys.argv[0], f"--workspace={...}", "launch"]                     # the path actually invoked
cmd = [sys.executable, "-m", "comfy_cli", f"--workspace={...}", "launch"]   # interpreter-anchored

sys.executable-based spawning would also match what resolve_python.py / uv.py already do.

Secondary note

Because the failure happens after the parent prints Launching ComfyUI from: <workspace>, it reads as though ComfyUI itself failed to start, which sends you looking at the workspace and its models rather than at the CLI. Catching FileNotFoundError around the spawn and reporting something like "could not re-exec comfy; is it on PATH?" would make the failure self-explanatory even before the fix above.

Nice to have

  • Terminal output
  • Screenshots

Additional context
Add any other context about the problem here.

Lenguaje dominante
Python
Estrellas
1k
Forks
176
Merge medio
1 d 11 h
PR fusionados (30 d)
87

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Comfy-Org/comfy-cli

Todos los issues de Comfy-Org/comfy-cli

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.