Running ComfyUI¶
Use cg run to launch ComfyUI from the selected ComfyGit environment.
Before launching, ComfyGit syncs the environment so the virtualenv, custom nodes, model links, PyTorch backend, and local overlays match the manifest plus local runtime configuration.
Choose An Environment¶
Use the active environment:
Or target one command:
Pass ComfyUI Arguments¶
ComfyGit owns flags before --. Arguments after -- are passed to ComfyUI.
Common examples:
One-Time Runtime Overrides¶
Use a different PyTorch backend for one run:
Apply an overlay for one run:
Install an optional extra for the run sync:
These operation-level flags do not rewrite the saved local environment config.
Skip Sync¶
Use --no-sync only when you deliberately want to bypass reconciliation. If the
runtime is stale, ComfyUI may start with missing packages, nodes, or model links.
Open ComfyUI¶
By default, ComfyUI is available at:
If you bind to 0.0.0.0, make sure the port is reachable from the browser or
machine that needs it.
Inspect And Restart A Managed Runtime¶
For a named environment launched by the current cg run supervisor:
Restart requires a matching runtime identity, reachable Manager restart support,
and a verified empty ComfyUI queue. It refuses unknown or busy state.
--wait verifies a new runtime generation and HTTP readiness; an accepted restart
request alone is not completion. If acknowledgement is uncertain, inspect status
before retrying.
A process started before upgrading the CLI must be stopped and relaunched through
the updated cg run to advertise this control endpoint. An arbitrary ComfyUI
process or port is not adopted. Existing legacy orchestrators retain their own
control path; do not use a named runtime request to restart a different child.
Run Vs Serve¶
cg run launches the full ComfyUI editor and backend.
cg serve fronts an already running ComfyUI backend with workflow contract
endpoints and the packaged Studio UI.
For Studio/API usage, run both:
Read more: Serve workflows.