配置文件丨导入

So you moved to a new machine, or an upgrade left your install in pieces, and you've got the comfyui_config_<timestamp>.zip that ConfigExport produced on the old box. ConfigImport is the other half of that round trip: you point it at the zip (or an extracted folder), and it restores the node list, frontend settings, dependency snapshot, workflows, and input/output files back into place. The important part is how carefully it does it - because the last thing you want from a "restore" is a freshly clobbered ComfyUI.

It's part of ComfyUI-QING's configuration-management category (display name 配置文件丨导入), and it's an OUTPUT_NODE: give it a path, it does the work, and reports a text summary through its result_analysis output.

How it works. Three inputs control the whole restore:

• import_path - the absolute path to your ZIP or folder. Required; the node refuses to guess.
• import_mode - the conflict policy, which is where the care comes in:
  • overwrite - replace existing files (the default).
  • skip - leave anything already on disk alone.
  • auto_rename - keep both, renaming the incoming file.
• create_backup - on by default; before it writes anything, it backs up the current config to your output directory.

It validates the path exists, handles zip-vs-folder automatically, and returns a result_analysis string describing what was imported, what was skipped or renamed, and whether a backup was made. If you've already made one with ConfigExport, the two line up: export → transfer zip → import.

How to install. ComfyUI-QING installs as one pack - search "ComfyUI-QING" in ComfyUI Manager, or:

cd ComfyUI/custom_nodes
git clone https://github.com/GAO-SHIQING/ComfyUI-QING
cd ComfyUI-QING
python install_dependencies.py

Restart afterward. The README's clone URL drops an "H" (GAOSHI-QING) - use the URL above or Manager. Add --mirror to the dependency step for China-based installs.

Troubleshooting. First, import_path must be absolute - relative paths just error out. Second, the mode you pick matters more than people expect: overwrite is fine for restoring a broken environment onto a clean one, but if you're importing into a working setup, skip or auto_rename is the safer call, and create_backup (on by default) is your undo button - check your output directory for the backup before you panic. Third, remember the limits of what config import covers: this restores node configs, frontend settings, dependency lists, and (if you exported them) workflows and input/output files. Model weights in models/ are not part of the bundle, so a fresh machine still needs its checkpoints. If ComfyUI won't start after import, the dependency list is a shopping list, not an install - you may need to actually pip install what the snapshot records.