WIP # WIP # WIP

scope-comfyui

A Daydream Scope plugin that runs ComfyUI workflows as real-time pipelines.

Users wrap ComfyUI nodes into a subgraph, promote the widgets they want exposed as controls, export the workflow JSON, and drop it into this plugin's workflows/ directory. Each workflow automatically becomes a Scope pipeline with UI controls generated from the promoted widgets.

How It Works

1. ComfyUI's subgraph system lets users bundle nodes into a single unit with explicitly chosen inputs (promoted widgets).
2. The plugin parses the exported workflow JSON, reads the subgraph definition and promoted widgets, and generates a Pydantic config class for each workflow.
3. At runtime, Scope's pipeline manager instantiates the pipeline, which uses the hiddenswitch/ComfyUI embedded client to execute the flattened workflow graph.

Installation

# 1. Install ComfyUI (--no-deps to avoid conflicts with Scope's torch, etc.)
uv pip install --no-deps "comfyui @ git+https://github.com/hiddenswitch/ComfyUI.git@87606c5"

# 2. Install this plugin (pulls in remaining execution deps)
uv pip install -e notes/scope_plugins/scope-comfyui

Usage

1. In ComfyUI, select the nodes you want to use and wrap them as a subgraph.
2. Promote the widgets you want to control from Scope (right-click a widget, "Promote to Subgraph Input").
3. Export the workflow as JSON and place it in scope_comfyui/workflows/.
4. Start Scope. The workflow appears as a pipeline with controls for each promoted widget.

Configuration

Edit scope_comfyui/config.yaml to point ComfyUI at your custom nodes and models:

# Primary workspace (custom_nodes/, models/, input/, output/ subdirs)
base_path: ~/.comfyui

# Additional search paths
base_paths:
  - /path/to/shared/models

# Fine-grained model paths (ComfyUI YAML format)
extra_model_paths_config:
  - /path/to/extra_model_paths.yaml

If your workflows use custom nodes, install their dependencies into the Scope environment separately.

Limitations (v1)

• One subgraph per workflow file (no nested subgraphs)
• New workflows require a server restart
• Image I/O between Scope and ComfyUI uses temp files
• No custom node installation management
• No VRAM estimation