Keep a reproducible ComfyUI repair record without exposing secrets

Record your own repair, not somebody else's case

This is our proposed evidence format. It does not reproduce a launcher's customer trace, telemetry counts or claimed success record.

pip inspect (available from pip 22.2) produces an environment report; pip check checks declared dependency compatibility. Import-to-distribution metadata mapping has limits, including some editable installations. Neither command proves GPU or workflow success.123

Use the interpreter that actually runs your ComfyUI instance; python below is a placeholder, not a guarantee that the system Python is correct. Check its pip version before using pip inspect; if that command is unavailable, record the version instead of changing packages just for this record.

python -m pip --version
python -m pip inspect > environment-before.json
python -m pip check

Review the full pip report locally before sharing: paths and installation origins may be private. Download the read-only environment inspector and run python inspect_environment.py with the same interpreter for a smaller metadata summary. Its own code does not install packages or read prompts, logs or tokens; normal Python startup hooks still apply. Distribution names and versions may themselves be sensitive, and --include-paths explicitly adds private interpreter paths. Review either output before sharing.

Use one controlled change

Keep a minimal workflow and input, record versions, explain one change, restart the same instance and retry the same task. ComfyUI's custom-node troubleshooting provides an isolation approach.4 Disabling a node is not proof that its previous dependency changes were undone.

Our suggested record is: original error, environment, change, rationale, new log, original-task outcome, rollback decision. Mark unperformed checks as unperformed. Successful installation, import and generation remain separate results. Keep unresolved conditions for later review instead of inheriting another site's verification badge.

Related checks

• Where to run ComfyUI commands: PowerShell, CMD and virtual environments
• Optional backend warnings: decide what blocks your workflow

Sources, script behavior and language parity rechecked 2026-09-25. The metadata script passed local unit tests; no ComfyUI repair, GPU or workflow reproduction is claimed. Upstream statements and our recommendations remain separate.