openclaw - 💡(How to fix) Fix Bundled comfy provider config schema/runtime mismatch in 2026.4.8 [1 participants]

Summary

Built-in comfy image generation in OpenClaw 2026.4.8 appears to have a config schema/runtime mismatch.

The runtime code for bundled comfy expects workflow settings like workflowPath, promptNodeId, and outputNodeId under models.providers.comfy, but the config schema rejects those keys there.

At the same time, the plugin manifest schema allows these workflow keys under plugins.entries.comfy.config, but the runtime does not seem to read from that location by default.

This makes the built-in comfy provider difficult/impossible to configure cleanly using valid config alone.

Environment

• OpenClaw: 2026.4.8
• Host: macOS arm64
• Built-in bundled comfy provider
• Local ComfyUI server

Symptoms

image_generate(action="list") showed:

• comfy (default workflow)
• models: workflow
• configured: no

Trying to configure workflow keys under models.providers.comfy caused config validation failure:

Invalid config at ~/.openclaw/openclaw.json
- models.providers.comfy: Unrecognized keys: "workflowPath", "promptNodeId", "outputNodeId"

What I found

Runtime behavior

Bundled comfy runtime code (dist/workflow-runtime-*.js) appears to read config from:

cfg?.models?.providers?.comfy

and requires fields like:

• workflowPath
• promptNodeId
• outputNodeId

It also determines configured state from those values.

Schema behavior

gateway config.schema.lookup for models.providers.comfy only exposes generic provider fields such as:

• baseUrl
• apiKey
• auth
• api
• headers
• request
• models

It does not allow:

• workflowPath
• promptNodeId
• outputNodeId

Plugin manifest behavior

Bundled comfy plugin manifest (dist/extensions/comfy/openclaw.plugin.json) appears to define workflow-specific config schema under plugin config, i.e. effectively:

• plugins.entries.comfy.config.workflowPath
• plugins.entries.comfy.config.promptNodeId
• plugins.entries.comfy.config.outputNodeId

So there seems to be a mismatch between:

• what the plugin config schema allows
• what the runtime actually reads

Reproduction

1. Enable bundled comfy provider
2. Configure valid ComfyUI base URL
3. Put workflow settings under plugins.entries.comfy.config
4. Restart gateway
5. Run image_generate(action="list")
6. Observe configured: no

If you instead move workflow keys under models.providers.comfy, gateway config validation rejects them.

Impact

The built-in comfy provider is registered, but a valid config path for workflow-based image generation is unclear / broken.

This can leave users in a state where:

• bundled comfy is visible in provider list
• but configured remains no
• and generation never reaches a usable state without patching runtime behavior

Suggested fix

One of these should be made consistent:

Option A

Treat workflow config as provider config and extend models.providers.comfy schema to include:

• workflow / workflowPath
• promptNodeId
• outputNodeId
• related comfy workflow keys

Option B

Keep workflow config under plugins.entries.comfy.config, but update runtime to merge/read that config source when resolving comfy provider config.

In either case, the config schema, runtime configured check, and generation path should all agree on the same config location.

Extra note from real testing

Once config resolution was manually aligned, built-in comfy/workflow generation worked against a real ComfyUI server.

So this looks like a configuration plumbing issue, not a core workflow execution problem.