comfy-build

Builds reproducible ComfyUI environments into versioned releases on the Comfy developer platform.

961|148|Updated Apr 14, 2024
One-click install
npx skills add https://github.com/Comfy-Org/comfy-cli --skill comfy-build
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comfy-build
Source: https://github.com/Comfy-Org/comfy-cli/tree/main/comfy_cli/skills/comfy-build
Command: npx skills add https://github.com/Comfy-Org/comfy-cli --skill comfy-build

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Packaging a working ComfyUI setup — its custom nodes, models, Python dependencies, and ComfyUI version — into a reproducible, deployable environment is error-prone and manual. This Skill turns a local install, a Desktop snapshot, a workflow JSON, or a written description into a committed comfy-build.yaml spec and a green, deployable release on the Comfy developer platform.

Core Features & Use Cases

  • Environment capture from any source: Scan a local ComfyUI install, import a ComfyUI Desktop snapshot, import a workflow JSON, or hand-author a definition from a Dockerfile, Modal script, or plain description.
  • Spec-driven build lifecycle: Manage the full init → validate → push → release flow against the builder, with resumable pushes, dry-run upload estimates, and conflict-checked spec sync.
  • Dependency pin guidance: Decide which pip pins to keep or drop before the first cut, predict dependency conflicts, and diagnose failed builds from logs and advisories.
  • Use Case: You have a local ComfyUI install with custom nodes and models and want a reproducible cloud environment. The Skill scans the install, writes comfy-build.yaml, prunes the pip freeze, pushes the spec, and cuts a linux/nvidia release you can later deploy.

Quick Start

Ask the assistant to build a reproducible ComfyUI environment from your local install using comfy build init, then validate, push, and cut a release for the linux/nvidia target.

Frequently Asked Questions about comfy-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a reproducible ComfyUI environment from my local install?

Run comfy build init on your install directory to scan it and write a comfy-build.yaml spec, then validate, push, and cut a release with comfy build release create. Pass --python pointing at the install's venv for split or Desktop layouts.

How do I create a ComfyUI build from a workflow JSON file?

Use comfy build init with --from-workflow pointing at the workflow file, which writes a local spec without creating a Build. Models named in the workflow are not included, so resolve each with comfy build refs resolve and set a ComfyUI version before cutting.

Why did my first ComfyUI build fail after scanning a local install?

The most common cause is init copying the entire pip freeze into pipDependencies, which the builder applies as overrides that can conflict with the base image's torch. Cut the first build with pipDependencies emptied, keeping only deliberate pins you can justify.

Can I import a ComfyUI Desktop setup into a build?

Yes, use comfy build init with --from-snapshot pointing at the Desktop snapshot JSON. The import requires cloud sign-in and carries no models, so use a direct scan instead when private model weights must be included.

What does a green or deployable release mean in comfy build?

A release is deployable when its linux/nvidia artifact reaches ready with an image ref, regardless of the rolled-up status. A release can show complete with failed targets, so check the deployable flag and per-target artifact states rather than status alone.

When should I not use comfy build?

Do not use it to deploy environments — it stops at a green release and hands off to comfy-deploy, which involves ongoing spend. It also requires the platform beta to be enabled on your account, and sign-in for any builder-facing operation.