Reference only

Manager cannot find Git: check the environment that launches ComfyUI

Git may work in one terminal but remain unavailable to a previously started launcher, service or container. Confirm the caller's executable search path.

Symptoms and scope

Git may work in one terminal but remain unavailable to a previously started launcher, service or container. Confirm the caller's executable search path.

Error fragments for search; IDs, values and filenames may vary:

Bad git executable
git is not recognized

Source-supported context

Manager exposes Git-related configuration, including git_exe in supported versions. A cloned repository and an extracted ZIP are not interchangeable for git pull. Source 1 Source 2

Cases to distinguish

1. Git is absent or not available on the launch process's PATH.

2. The process was started before Git or PATH was updated.

3. A service account, container or launcher uses a different environment from the interactive terminal.

Diagnostic sequence

The sequence below is an editorial procedure based on the cited context, not a diagnosis already confirmed for your environment.

Step 1. Run git --version in the same execution context used to start ComfyUI.

Step 2. Use the official Git installation route and a correct PATH, or the version-appropriate Manager git_exe setting.

Step 3. Fully restart the relevant process after changing its environment; refreshing the webpage is not sufficient.

Step 4. Check whether the target node directory is an actual Git checkout before attempting an update. Preserve local changes before any repair.

Completion check

The calling process can invoke Git and perform the intended repository operation. Authentication and network failures that follow are separate issues.

Limitations and cautions

Avoid global reset/cleanup scripts. A ZIP installation should not be forcibly treated as a healthy Git repository.

Original sources

Localization prepared: 2026-09-22. The source-check dates above were inherited from the existing article; this translation does not claim they were all rechecked today. No GPU run, minimum-memory measurement or runtime guarantee is supplied.

Didn't solve it?

Check the next possible cause

The same symptom can come from a different cause. Work through these related entries in order.

  1. ComfyUI Manager button missing: distinguish UI changes from load failuresComfyUI-ManagerDesktop, newer Manager interfaces and legacy installations do not necessarily expose Manager in the same place or install it in the same way.
Paste your full log into the error finder

Was this page helpful?

Anonymous. Only a yes/no counter is stored; no account, IP address or device details.

Sources & references

Localized from the existing Chinese research draft. Original source-check dates are retained; this translation is not new technical verification or a runtime test.

01ComfyUI Manager troubleshootingSource checked: 2026-09-2102Install custom nodesSource checked: 2026-09-21

Report an issue · 1540e9fc-2130-5d66-8c7c-2c632cd44338