ComfyUI Setup Manager v0.8.8

ComfyUI Setup Manager v0.8.8

This maintenance release improves installation and prerequisite documentation.

Documentation

• Added a comprehensive prerequisite guide for Windows, Linux, WSL2, and macOS.
• Documented WinGet requirements for the Windows bootstrap installer.
• Documented manual Python and Git installation alternatives.
• Added a dedicated Badgids Complete profile installation guide.
• Kept Badgids Complete-specific requirements separate from the core manager prerequisites.
• Documented optional source-build and acceleration dependencies.
• Corrected documentation links in the packaged installer README.
• Added documentation regression tests.

Related changes

• Merged PR #2.
• Resolves the reported missing WinGet prerequisite documentation.

comfyui-setup-manager-v0.8.7

First official public release of comfyui-setup-manager v.0.8.7

ComfyUI Setup Manager is a standalone application for installing, launching, updating, repairing, inspecting, exporting, importing, and sharing ComfyUI installations, models, and workflows.

It provides:

• a compact Textual terminal interface for people;
• a complete non-TUI command-line interface for scripts and automation;
• portable YAML-based setup profiles;
• shared external model and workflow libraries;
• update snapshots and rollback;
• a YAML-backed runtime cache for fast startup and explicit rescans;
• dedicated workspaces for nodes, workflows, models, LoRAs, Agent Skills, and MCP definitions;
• editable source catalogs for models, LoRAs, workflows, Python wheels, and repositories;
• filesystem autocomplete and a built-in TUI file browser for path and file fields;
• a project-local profiles/ directory for portable profile exports, with migration from the former setups/ name and immediate profile-library refresh;
• managed runtime-log rotation, browsing, search, clipboard copy, deletion, and configurable retention;
• dependency reconciliation and ComfyUI custom-node startup validation before an installation is marked complete;
• selectable, scrollable, theme-derived syntax coloring in every path/input, console, inventory, review, and diagnostic output surface, with normal mouse and keyboard copy shortcuts and plain-text clipboard output.

Every important TUI action has a CLI command. CLI output can be text, JSON, or YAML.

Release notes — 0.8.7

Theme-aware readable output with plain-text copying

• Runtime follow logs, installation/update/snapshot consoles, task output, node/plugin inventories, workflows, models, LoRAs, skills, MCPs, YAML, JSON, and supported source editors now use semantic syntax roles derived from the active built-in or imported theme.
• Logs recognize errors, warnings, successful steps, commands, timestamps, requirements, paths, and URLs. Inventories distinguish names, paths, sizes, sources, and state labels.
• Coloring exists only in Textual's render-time highlight map. The selectable document, copied selection, clipboard/cache, and persisted logs contain sanitized plain text with ANSI, OSC hyperlink, Rich markup, and color escapes removed.
• Large cached inventories and runtime-log tails are inserted in batches so syntax highlighting does not introduce per-line redraw lag.

Transactional profile file editor

• Profile Library adds Edit profile files for imported .comfyuisetup archives.
• UTF-8 YAML, JSON, source, README, dependency-manifest, embedded-plugin, and forward-compatible text members can be edited with line numbers and language-aware highlighting; generated metadata, binary payloads, and text over 2 MiB remain protected.
• Save creates a separate candidate, rebuilds the canonical profile, recalculates profile/payload/manifest/wheel integrity data, preserves unknown safe members, and replaces the original only after complete validation.
• Invalid syntax, schema, payload, checksum, or in-library ID changes leave the original bytes untouched.
• CLI parity is available through profiles files, profiles read-file, and profiles edit-file.

Consistent profile directory and manual authoring

• Project-local portable exports now use profiles/ instead of setups/.
• On first use, non-conflicting legacy files move into profiles/; existing same-named destinations are never overwritten, and the old directory is removed only when empty. setups_directory() remains a compatibility alias for integrations.
• New linked documentation explains by-hand .comfyuisetup, native workflow JSON, and .comfyworkflows creation/editing, canonical extensions, authoritative companion files, checksum formulas, safe paths, validation commands, and the difference between a workflows directory and a workflow-pack extension.

Release hardening

• Source-tree managed launches resolve inherited relative Python package paths before switching into the ComfyUI checkout, so the detached runtime-log relay starts reliably from development and portable source environments.
• A required core update package is included automatically when callers use the checked default selection, even if an integration mutates the preflight requirement flag after selection state was built.

0.8.6 feature set

Current-install update and action-accessibility correction

• Already-current installations no longer perform an unnecessary uv dependency dry run. A passing current pip check is reported with protected resolution not needed.
• File-only updates and compatible manifest-only changes do not invoke pip. Only reviewed core packages whose installed versions fail the target requirement are submitted to the resolver.
• Custom-node requirement files remain audit and direct-conflict evidence, but are not installed as a new global recipe. Installed metadata, pip check, and full ComfyUI/custom-node startup validation remain authoritative.
• Duplicate or stale dist-info records that normalize to the same project, such as two visible tensorrt-cu13-libs versions, are reduced to Python's effective installed distribution before constraints are written.
• Every installed non-core package and every unselected core package is protected during a package change.
• Try to patch current setup and Continue anyway remain enabled for a real pending update after a protected dry-run failure. They still snapshot first and roll back automatically on failure.
• Update controls now live in a fixed action dock above the footer, independent of the scrolling review and console.

0.8.5 feature set

Transactional customized-install updates

• Official ComfyUI core file and direct core-library changes are now displayed for review and are allowed unless they break a protected part of the environment.
• Preflight reports changed files, selectable direct package changes, protected packages, Python support, current pip check, custom-node conflicts, compiled/accelerator ABI risk, profile locks, Git customization, and a protected uv dry run.
• The updater no longer invokes the checkout's requirements.txt and manager_requirements.txt as separate install commands. It parses selected core requirements and custom-node manifests into one audited resolver input.
• Non-core compiled packages, profile-owned packages, local/direct artifacts, and accelerator packages are constrained at their known-working versions. Core libraries remain eligible to move when the complete plan stays compatible.
• The TUI provides Safe update, Try to patch current setup, Continue anyway, Create new install, and Abort update, with individual selection of reviewed core package changes.
• Resolver, pip check, server-ready, module-import, or custom-node startup failure after mutation automatically restores the source/package snapshot and reports rollback validation.
• Creating a separate install from an unmanaged customized checkout first captures an exact portable profile. Successful-update inventory refresh uses a visible background progress screen.

PEP 440 profile versions and ABI identity

• New .comfyuisetup exports normalize their profile version according to PEP 440.
• Exact profiles record and display complete Python, CUDA/ROCm/CPU/MPS, and PyTorch build identity plus a combined tag such as cp312-cuda124-torch2_6_0_cu124.
• The tagged name, readable compatibility values, version, and creation data appear in Setup & Install, Profile Library, profile.yaml, metadata.yaml, the archive README, and installation reports.
• Legacy profiles remain readable; compatibility metadata is derived when possible and marked as a compatible target when it is not an exact captured ABI.

This patch prevents installation failures and post-install inventory refreshes
from blocking the Textual interface while retaining the exact-profile fixes
from 0.8.3.

TUI responsiveness correction

• Unexpected installation-worker failures now become an ordinary failed
  InstallResult; the recovery shell, Retry, Return Home, and Quit controls are
  restored even when failure happens outside the engine's normal error boundary.
• Closing an installation screen releases pending administrator-password and
  wheel-source prompts so a background worker cannot strand application exit.
• Return Home no longer invokes installation discovery synchronously on the UI
  thread. The dashboard appears immediately and a progress modal reports the
  background inventory refresh.
• The newly installed target is selected only after discovery completes, so the
  dashboard and Launch & Manage tab use the refreshed cache consistently.
• Added TUI regressions for exceptional worker failure, restored controls,
  visible scan progress, asynchronous Home navigation, and final target selection.

Exact-profile installation correction

• Final environment verification now treats CPU/GPU variants that expose the
  same import package as mutually exclusive providers. An exported NVIDIA
  profile using onnxruntime-gpu no longer incorrectly demands a second
  overlapping onnxruntime installation merely because stale metadata for both
  existed in the long-lived source environment.
• Existing 0.8.2 exact profiles that recorded PyOpenGL-accelerate in the
  authoritative environment lock but omitted its acceleration descriptor are
  repaired automatically during planning and installation.
• New exports include a portable, version-pinned PyOpenGL-accelerate
  descriptor for Windows, Linux, and macOS across supported accelerators.
• Regression coverage exercises old-profile recovery, exact exporter output,
  provider-family verification, and rejection of genuinely unexpected packages.

Same-version node-lifecycle and acceleration-build correction

• Repositor...