function getComfyConfig(cfg) { const raw = cfg?.models?.providers?.comfy; return isRecord(raw) ? raw : {}; } But putting config there fails validation:

Nested format (from docs): models.providers.comfy: Unrecognized keys: "mode", "image" Flat legacy format: models.providers.comfy: Unrecognized keys: "allowPrivateNetwork", "workflowPath", "promptNodeId", "outputNodeId" With models: [] added: models.providers.comfy: Unrecognized keys: "mode", "image" The models.providers validator only accepts standard LLM provider keys (baseUrl, apiKey, models, api). Comfy-specific keys are always rejected.

Config that works (accepted by validator, but runtime can't see it) { "plugins": { "entries": { "comfy": { "enabled": true, "config": { "mode": "local", "baseUrl": "http://192.168.1.112:8188", "allowPrivateNetwork": true, "image": { "workflowPath": "~/.openclaw/workspace/comfy-workflows/flux-schnell.json", "promptNodeId": "6", "outputNodeId": "12" } } } } } } Docs reference

https://docs.openclaw.ai/providers/comfy shows config under models.providers.comfy with nested image/video/music blocks, but this is rejected by the validator in 2026.4.5.

Confirmed by Discord support

Krill confirmed this is a regression — no config-only workaround exists in this version.

Steps to reproduce

1. Install OpenClaw 2026.4.5
2. Run npx openclaw onboard --auth-choice comfy — configures plugins.entries.comfy.config with mode, baseUrl, allowPrivateNetwork, image workflow
3. Set agents.defaults.imageGenerationModel.primary to comfy/workflow
4. Have ComfyUI running on LAN (e.g. 192.168.1.112:8188)
5. Call image_generate with model comfy/workflow
6. Error: models.providers.comfy.<capability>.workflow or workflowPath is required
7. Move config to models.providers.comfy as documented → validator rejects Comfy-specific keys: "Unrecognized keys: mode, allowPrivateNetwork, workflowPath, promptNodeId, outputNodeId, image"

Expected behavior

image_generate with model comfy/workflow should generate an image via the configured ComfyUI instance, using the workflow JSON, promptNodeId, and outputNodeId from the config.

Actual behavior

Runtime reads config from cfg.models.providers.comfy (getComfyConfig in workflow-runtime), but:

1. Onboard (--auth-choice comfy) writes config to plugins.entries.comfy.config — runtime never reads from there
2. Putting config in models.providers.comfy fails validation — all Comfy-specific keys rejected as "Unrecognized keys"
3. Result: no valid config path exists. image_generate always fails with "models.providers.comfy.<capability>.workflow or workflowPath is required"

OpenClaw version

OpenClaw 2026.4.5 (3e72c03)

Operating system

macOS 25.3.0 ARM64 (Mac Mini M4 Pro)

Install method

npm install -g openclaw Node v22.22.1

Model

anthropic/claude-opus-4-6

Provider / routing chain

Anthropic API direct (api-key auth)

Additional provider/model setup details

Model: anthropic/claude-opus-4-6 Provider/routing: Anthropic API direct (api-key auth) Additional: ComfyUI configured as image generation provider (comfy/workflow), not as LLM provider

Logs, screenshots, and evidence

TL;DR

The most likely fix for the ComfyUI plugin configuration issue in OpenClaw 2026.4.5 is to update the configuration reader to accept Comfy-specific keys or modify the validator to allow these keys.

Guidance

1. Identify the configuration mismatch: The onboard process writes to plugins.entries.comfy.config, but the runtime reads from models.providers.comfy. This mismatch causes the configuration to be unreadable by the runtime.
2. Modify the configuration reader: Update the getComfyConfig function in workflow-runtime-CVir5_fU.js to read from plugins.entries.comfy.config instead of models.providers.comfy.
3. Update the validator: Modify the validator to accept Comfy-specific keys, such as "mode", "image", "allowPrivateNetwork", "workflowPath", "promptNodeId", and "outputNodeId".
4. Test the configuration: After making the necessary changes, test the configuration by running the image_generate command with the model comfy/workflow to ensure that it generates an image via the configured ComfyUI instance.

Example

// Modified getComfyConfig function
function getComfyConfig(cfg) {
    const raw = cfg?.plugins?.entries?.comfy?.config;
    return isRecord(raw) ? raw : {};
}

Notes

The provided solution is based on the information given in the issue and may not be a complete fix. It is recommended to test the changes thoroughly and consult with the OpenClaw support team if issues persist.

Recommendation

Apply a workaround by modifying the configuration reader and validator to accept Comfy-specific keys, as updating to a fixed version is not currently an option. This will allow ComfyUI image/video/music generation to function in OpenClaw 2026.4.5.