How does frontend pinning relate to workflow portability and to the frontend and untrusted-workflow security advisories?
Problem. Choosing between the pip frontend, a pinned GitHub release and a local root when sharing workflows or hardening a machine. Conditions. Reproducing a workflow (C3-B746, C3-B590-05) or responding to frontend advisories (C3-B710-09/09). Method. The default path is a pip package with a version pin in requirements.txt, and ComfyUI logs a warning at startup if comfy* packages are below that requirement; updating means upgrading that pip package. --front-end-version overrides it per launch from GitHub releases and caches by folder; --front-end-root points to any local build and bypasses version management. The official docs list both flags with the same wording as the code. Failure modes. Because a failed pin falls back silently to the pip frontend (C3-B807-02), a portability note that says 'pinned to 1.x' should be checked against the running frontend, and a security fix delivered in a newer frontend is not applied by a pin to an older release. Limitations. I did not find a docs....
Structured fields
{
"citations": [
{
"url": "https://docs.comfy.org/llms-full.txt",
"note": "llms-full.txt CLI arguments table; llms-full.txt CLI arguments table; frontend_install_warning_message; researcher reasoning"
},
{
"url": "https://raw.githubusercontent.com/comfyanonymous/ComfyUI/fb3befd168731438f88bc96e0920a538e8649878/app/frontend_management.py",
"note": "llms-full.txt CLI arguments table; llms-full.txt CLI arguments table; frontend_install_warning_message; researcher reasoning"
}
]
}Evidence claims
- [sourced_fact] Problem. Choosing between the pip frontend, a pinned GitHub release and a local root when sharing workflows or hardening a machine. Conditions. Reproducing a workflow (C3-B746, C3-B590-05) or responding to frontend advisories (C3-B710-09/09). Method. The default path is a pip package with a version pin in requirements.txt, and ComfyUI logs a warning at startup if comfy* packages are below that requirement; updating means upgrading that pip package. --front-end-version overrides it per launch from GitHub releases and caches by folder; --front-end-root points to any local build and bypasses version management. The official docs list both flags with the same wording as the code. Failure modes. Because a failed pin falls back silently to the pip frontend (C3-B807-02), a portability note that says 'pinned to 1.x' should be checked against the running frontend, and a security fix delivered in a newer frontend is not applied by a pin to an older release. Limitations. I did not find a docs.comfy.org page beyond the aggregated CLI argument table; advisory content itself was not re-read here, so linkage to C3-B710 is by topic. Version and date. 2026-10-24. · locator: llms-full.txt CLI arguments table; llms-full.txt CLI arguments table; frontend_install_warning_message; researcher reasoning source
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| documentation | unknown | permitted | permitted | unknown | unknown | Applies to this original summary only, not to the cited sources. |