ComfyUI addon

ComfyUI integration for AYON.

To learn more about configuration and user guides, please visit AYON ComfyUi - AYON Help Center.

A note on https:

The planned control flow is as follows:

[AYON]--> WebSocket Server(WSRPC) <---> [AYON HTTP server w/ <iframe>]
  |                                                    ^ Continuous polling for WebUI buttons to function.
  | heartbeat (WebSocket Client)                       | 
  V                                                    V postMessage "Ayon API" requests
[ComfyUI Backend] -> Middleware -> [ComfyUI Frontend]

This requires, that said Middleware respects the <iframe> specifications for embedding pages of cross-origin. This is done through headers.

If your comfyui server is just being forwarded without:

• X-Frame-Options
• Content-Security-Policy

being injected into the headers, you have nothing to worry about,
except that you may want to follow the advice to put a Content-Security-Policy header in place.

Content-Security-Policy: frame-ancestors http://localhost:<port_that_iframe_is_hosted_on>;

Security notice

Warning

This explicitly allows mixed security and (limited; ASSUMING Content-Security-Policy) cross-origin remote scripting.

More information (including header settings and further security issues) is provided here.

Caveats

Multi-Tab / RPC Limitations in ComfyUI Addon

A quick heads-up on how ComfyUI handles browser sessions:

• Single RPC Connection: The addon isn't built to handle multiple open tabs simultaneously because the RPC connection can only link to one tab at a time.
• No Multi-Tab Execution: Only the active tab responds. There isn't an API method to switch tabs remotely or push executions to inactive tabs.
• Session Data Inspection: ComfyUI manages different workflow tabs internally by dumping stringified project JSONs into browser session storage. The addon works around this by identifying the active tab and extracting the relevant workflow state from that session data.