Integrating ComfyUI into an app: prefer an explicit service boundary

This is an integration problem, not an interpreter mismatch

Discussion about embedding main.py belongs to application integration. ComfyUI documents task submission, history, file retrieval and WebSocket routes. 1 We recommend using an explicit service boundary rather than treating an entry script as a stable library contract.

Start with a read-only request to a service you control:

curl --fail http://127.0.0.1:8188/system_stats

For a remote instance, configure the actual server address. A successful response verifies this route only, not task submission, authentication or result delivery.

Our proposed business layer tracks task identifiers and separates connection, validation, execution and download failures. After a submission timeout, investigate whether a task was accepted before resubmitting and accidentally duplicating work.

Keep filesystem access constrained and protect any network-facing execution service. Validate one end-to-end task, then test disconnects, timeouts and cancellation against the selected version. This is an architecture recommendation, not a claim that ComfyUI provides a stable embedded-Python SDK or that this package has already deployed one.

Related checks

• ComfyUI Failed to fetch: identify the request before reinstalling
• ComfyUI workflow save failed: preserve the canvas before troubleshooting

Source-reviewed editorial guidance; no local/GPU execution or embedded-Python SDK guarantee. Indexing remains withheld by site-wide gates.