Skip to content

ComfyUI-Doctor 2.1.0

Latest

Choose a tag to compare

@rookiestar28 rookiestar28 released this 25 Oct 11:36
· 1 commit to main since this release

ComfyUI-Doctor 2.1.0

Changes since v1.9.0.

This release improves compatibility with current ComfyUI hosts, makes workflow diagnostics and
node navigation more accurate, and strengthens LLM destination and credential handling.

Host compatibility and node navigation

  • Maintain separate source-contract lanes for Desktop frontend 1.43.18, ComfyUI-pinned frontend
    1.57.1, and standalone frontend 1.59.1, including asynchronous settings, execution events,
    asset previews, named widget restoration, validation errors and job-cancel contracts.
  • Preserve numeric and opaque string node IDs, including IDs containing colons, throughout
    diagnostics, signature targets, asset correlation, Locate Node and permitted fixes.
  • Resolve root nodes, executable groups and real subgraphs distinctly. Ambiguous IDs cannot
    authorize a fix, and stale, removed or superseded targets cannot focus a different workflow.
  • Keep special-character node IDs inert in the latest-diagnosis Locate button, preventing
    attribute/event-handler injection while preserving the exact target.
  • Enforce the Doctor sidebar's 560px minimum without overriding wider user layouts. Switching to
    another custom sidebar releases Doctor's layout and lifecycle ownership.

More accurate local diagnostics

  • Recognize optional first-party Switch and Branch inputs without suppressing genuine required
    inputs or broken links. ComfyUI still validates the selected branch when executing a workflow.
  • Use the live ComfyUI model registry and registered extensions, inspect bounded nested/promoted
    workflow assets, and support positional-first widget values with bounded named-value fallback.
  • Cover more first-party model, image, video, audio and dataset loader families, including the
    SAM3D Body detection root. Preserve visible-node and concrete source-loader provenance.
  • Contain asset paths within authoritative roots before probing them; reject traversal, external
    paths, cross-drive candidates and symlink escapes. Check dataset folders without reading contents.
  • Align Python/PyTorch guidance with host support, stop penalizing missing optional xFormers,
    and show bounded nonfatal guidance for recognized DynamicVRAM fallback warnings.
  • Improve validation-error grouping, missing-model/media guidance, public subgraph boundaries,
    partner workspace-policy errors and duplicate validation/runtime report suppression.
  • Correct privacy checks, pattern-category summaries, local telemetry pattern recognition and
    per-node-type failure statistics derived from stored history.

LLM destination, credential and UI safety

  • Limit LLM requests to built-in provider destinations, supported local Ollama/LM Studio endpoints,
    and exact additional base URLs registered by the server operator. Refuse other destinations
    before sending a network request.
  • Bind server-held credentials to their approved destination. A different endpoint needs an
    explicitly supplied key instead of inheriting a server environment or stored credential.
  • Keep encrypted credential stores locked when the encryption key is unavailable or different;
    restoring the original key recovers access without replacing the stored credentials.
  • Redact Authorization and X-API-Key values unconditionally, and opt Doctor-owned settings
    out of host setting-change telemetry where the host supports it.
  • Render fix suggestions and dynamic status text as inert content. Permitted fixes require an
    exact live node, an allowed widget and a valid value.

Chat, startup and rendering reliability

  • Fix chat before the first captured error, surface request failures instead of a stuck
    placeholder, support stopping a running reply, and apply the configured chat token budget.
  • Load markdown and code highlighting from Doctor's own extension folder even when that folder
    is renamed; missing rendering assets fall back to plain text without a CDN fallback.
  • Scope Chat island lifecycle operations to their owned pane and retain vanilla UI fallbacks.
  • Unify Doctor startup logging, keep persisted/plain output free of ANSI styling, and restore
    the full compact startup banner with an encoding-safe ASCII fallback.
  • Keep Desktop runtime identification independent of private state-directory selection and
    preserve ComfyUI package-loading behavior during tests.

Development and dependency maintenance

  • Patch Vite to 6.4.4, PostCSS to 8.5.25 and esbuild to 0.28.1; refresh Vitest and related
    development dependencies. Offline regressions check security-sensitive locked dependency floors.
  • Refresh host source contracts without running code from host reference checkouts.
  • Use normal importlib package loading in the route harness and mandatory isolated checks for
    the Registry's S102, S307 and E702 security rules across tracked Python files.
  • Expand real route-handler coverage, source-mutation-free backend collection, deterministic
    telemetry integration/stress lanes and host-shaped frontend asset tests.
  • Update the user, architecture, API and validation documentation and keep release metadata aligned.

Upgrade notes

  • Restart ComfyUI after updating. Python 3.10+ remains supported; base PyTorch guidance remains 2.7+.
    Automatic DynamicVRAM has its separate PyTorch 2.8+ requirement and 2.12+ recommendation.
  • Custom remote LLM endpoints must be registered on the ComfyUI server through
    DOCTOR_LLM_ALLOWED_BASE_URLS or the documented provider base-URL environment settings.
    See Configuration and Security.
  • Preserve the original credential-store encryption key. Changing it locks the store until the
    original key is restored; Doctor does not silently replace an unreadable encrypted store.
  • A previously acknowledged issue for a numeric-string node ID may reappear once because its
    issue identifier now preserves the original ID type. Malformed/duplicate node identities may
    still omit findings on those nodes; unrelated valid-node findings remain available.
  • Frontend E2E tooling supports Node.js 18 through 25; use Node.js 24 for the current Vitest unit lane.
    Node.js is development tooling and is not needed to run the installed Doctor node.
  • Source compatibility checks and mocked UI tests do not establish live-host certification or
    guarantee support for every custom node and malformed workflow.

Full comparison