Skip to content

v1.8.0

Choose a tag to compare

@rookiestar28 rookiestar28 released this 26 Apr 12:32
· 90 commits to main since this release

ComfyUI-Doctor v1.8.0

This release focuses on the LLM analysis pipeline, provider handling,
host compatibility, security hardening, API consistency, and public
documentation cleanup since v1.7.5.

Highlights

  • Unified the LLM context construction path through the analysis pipeline.
    Prompt context now flows through structured handling for sanitized
    tracebacks, node context, recent logs, workflow snippets, and system
    details.

  • Added a centralized LLM provider adapter layer.
    OpenAI-compatible providers, Anthropic, and Ollama now share unified
    request and response handling across chat, analysis, model listing,
    and provider connectivity checks.

  • Improved node-context reliability.
    Recent workflow execution errors now use validated, immutable node
    identity data for analysis, locate actions, and prompt context.

  • Standardized Doctor API error responses.
    API failures now return consistent JSON error envelopes with success,
    error, and message fields while preserving existing success shapes.

  • Strengthened frontend compatibility with newer ComfyUI settings APIs.
    Doctor now prefers the current ComfyUI settings API while keeping
    isolated fallback behavior for older host environments.

  • Improved execution-error lineage enrichment.
    Doctor can better connect bare execution errors to recent progress and
    execution events when ComfyUI provides enough event data.

LLM and Analysis Improvements

  • Routed LLM prompt context through the analyzer pipeline instead of
    relying on partial manual composition.

  • Deduplicated error-analysis prompt templates to reduce drift between
    local analysis and LLM-assisted analysis paths.

  • Added provider adapter tests covering normalized request/response
    behavior for supported provider families.

  • Kept provider-specific behavior isolated so future provider changes can
    be implemented with lower risk.

Security and Privacy

  • Added strict admin-token enforcement for shared-server deployments.

  • Documented server-side credential storage metadata and the current
    encrypt-then-MAC design.

  • Improved import fallback behavior to avoid unsafe or ambiguous absolute
    fallback paths.

  • Updated outbound safety documentation and checker behavior.

  • Refreshed the secrets baseline after public-safe repository cleanup.

Diagnostics and Stability

  • Removed the obsolete placeholder diagnostics check now that concrete
    local diagnostics checks are available.

  • Fixed logger reset synchronization so processor state is cleared more
    reliably when history is reset.

  • Added host-like package/startup validation coverage to catch ComfyUI
    host-loading regressions earlier.

  • Added compatibility smoke coverage for the ComfyUI, frontend, and
    desktop surfaces Doctor depends on.

Testing and CI

  • Added an optional coverage baseline workflow and local coverage script.

  • Installed missing coverage test dependencies in the development
    requirements.

  • Expanded backend regression coverage for:

    • LLM context pipeline behavior.
    • Provider adapter normalization.
    • Immutable node context handling.
    • API error response envelopes.
    • Logger reset behavior.
    • Import fallback policy.
    • Diagnostics registry cleanup.
    • Host compatibility checks.
    • Coverage baseline script behavior.
  • Expanded frontend E2E coverage for:

    • Modern ComfyUI settings API compatibility.
    • Execution-error lineage enrichment.
    • Sidebar locate behavior.
    • Statistics and telemetry surfaces.

Upgrade Notes

  • No known breaking changes are expected for normal ComfyUI custom-node
    usage.

  • Shared-server operators should review the admin-token settings:

    • DOCTOR_ADMIN_TOKEN
    • DOCTOR_REQUIRE_ADMIN_TOKEN=1
  • Local single-user desktop setups can continue using loopback convenience
    behavior where appropriate.

  • Developers should use the updated full-test scripts for CI-parity
    validation before publishing further changes.