Skip to content

Options and Maintenance

Jump to bottom
Dariusz L edited this page Aug 3, 2026 · 1 revision

Options and Maintenance

Open Model Resolver > Options to configure downloads, searches, workflow behavior, local databases, and logs.

Search defaults

  • Auto-fill model filter starts a new search with the detected workflow base model.
  • Auto-fill subfolder fills a download subfolder from metadata, filename patterns, and existing folders.
  • Refresh ComfyUI models after Apply refreshes model catalogs when the applied file is not visible yet.
  • Open when a workflow has missing models opens Model Resolver after analysis finds unresolved references.
  • Embed workflow hashes stores SHA-256 model metadata in saved workflow data.
  • Embed opener node adds the Model Resolver dependency node to saved workflow data.

The source toggles in Download Sources control which providers the Everything search uses. A disabled source stays out of that search and cannot run until you enable it again.

Download paths

The Paths section controls:

  • Download backend.
  • aria2 path and idle daemon shutdown.
  • Download Path Mode.
  • Default model roots.
  • Per-category path templates.
  • Base Model Path Mappings.

Path settings affect new downloads. The folder and subfolder controls on each download remain available for one-off changes.

Use Detect path templates to inspect existing folders and suggest patterns. Review the result before saving it.

Provider settings

The CivitAI and HuggingFace sections store credentials and search methods. Each credential has a Check action. A valid credential does not grant access to a provider's restricted content by itself. The provider may still require accepted terms or repository permissions.

Local Database

The Local Database section manages cached provider data:

  • Model list checks and updates the ComfyUI-Manager model-list.json catalog.
  • Base Models checks and updates CivitAI base-model names and aliases.
  • Hugging Face author index refreshes the public author fallback index.

These actions update local metadata files inside the extension. They do not download model weights.

Metadata tools

Metadata Size Audit

Check Metadata Sizes compares stored model sizes with the files on disk. The results show scanned models, checked metadata, mismatches, missing sizes, and errors.

Local Metadata Builder

The builder creates or updates local model metadata. Choose one mode:

  • Calculate SHA-256 from scratch reads each model file and calculates a new hash.
  • Use existing plugin metadata imports metadata already available to the extension.

Set the number of concurrent hash workers according to your disk speed. Hashing large model collections can use substantial disk I/O. The builder reports progress, history, skipped entries, hashes, and errors. You can cancel a running job.

Logs and cache

The Maintenance section provides:

  • Frontend and backend log switches.
  • Separate frontend and backend log levels.
  • Frontend and backend log export.
  • A combined frontend/backend cache clear action.

Cache clearing does not delete model files, metadata files, saved options, or API keys. Keep exported logs private when they contain local paths or provider error details.

Clone this wiki locally