Skip to content

fix(comfyui): real ComfyUI link + workflow tags open the editor#881

Merged
thinmintdev merged 1 commit into
mainfrom
feat/comfyui-link-fix
Jun 17, 2026
Merged

fix(comfyui): real ComfyUI link + workflow tags open the editor#881
thinmintdev merged 1 commit into
mainfrom
feat/comfyui-link-fix

Conversation

@thinmintdev

Copy link
Copy Markdown
Contributor

Why

The dashboard ComfyUI card's open-link came from the /status endpoint field (":8188"), which old code turned into http://127.0.0.1:8188 — the server's loopback, dead from a browser. And the six workflow tags POSTed to /workflows/{name}/launch with names (qwen-image…) that don't match the real workflow files, so they 404'd silently. Together: "the workflow tags aren't linked."

What

  • Backend (/api/config/urls): new comfyui key — HAL0_COMFYUI_PUBLIC_URL env override, else http://<request-host>:8188, proxy-aware (port-stripped behind a proxy). Mirrors the existing openwebui pattern so a reverse-proxy deploy can advertise a clean HTTPS URL and avoid the mixed-content block an HTTPS dashboard hits on a bare :8188 link.
  • Frontend: comfyBaseUrl now derives from useConfigUrls().comfyui (with a window.location:8188 fallback for the pre-config tick), not the dead loopback. The workflow tags are now anchor links that open ComfyUI's editor (matching the block's own "opens in ComfyUI ↗" label) instead of the broken headless launch. Each carries a forward-compatible ?workflow=<file> breadcrumb pointing at the curated workflow.

Upstream note

True per-workflow auto-open via URL is blocked upstream (comfyanonymous/ComfyUI#9858). The ?workflow= param is ignored by current ComfyUI (link opens the editor, where the curated workflows are now pickable) and auto-upgrades to a true deep-link if/when #9858 ships. The backend launch route is left in place (still tested).

Tests

  • 3 new backend tests for the comfyui URL (LAN-direct :8188, env override wins, proxy without env). test_config_urls.py 13/13 green.
  • Updated comfyui-arbiter-v3 e2e: workflow chip is now an anchor opening ComfyUI in a new tab. Affected specs 17/17 green; npm run build + tsc --noEmit clean.

Related runtime fix (already applied on CT105, not in this PR)

The 10 curated workflows (Qwen-Image, Wan2.2, LTX2, Hunyuan) were saved in ComfyUI API format in the editor's user/default/workflows dir, so ComfyUI's workflow browser rendered them blank. Converted in place to graph format via ComfyUI's own loadApiJson (backup at workflows.api-bak). They now open as real graphs.

🤖 Generated with Claude Code

The dashboard ComfyUI card derived its open-link from the /status
`endpoint` field (":8188"), which old code turned into
http://127.0.0.1:8188 — the *server's* loopback, dead from a browser.
And the six workflow tags POSTed to /workflows/{name}/launch with names
("qwen-image"…) that don't match the real files, so they 404'd silently
— the "tags aren't linked" report.

- Backend: /api/config/urls now returns a `comfyui` key (env
  HAL0_COMFYUI_PUBLIC_URL, else http://<request-host>:8188, proxy-aware,
  port-stripped behind a proxy) — mirroring the openwebui pattern so a
  reverse-proxy deploy can hand back a clean HTTPS URL and avoid the
  mixed-content block an HTTPS dashboard hits on a bare :8188 link.
- Frontend: comfyBaseUrl now comes from useConfigUrls().comfyui (with a
  window.location:8188 fallback for the pre-config tick), not the dead
  loopback. The workflow tags become anchor links that open ComfyUI's
  editor (matching the block's "opens in ComfyUI ↗" label) instead of
  the broken headless launch. Each carries a forward-compatible
  ?workflow=<file> breadcrumb (ComfyUI#9858) pointing at the curated
  workflow — ignored by current ComfyUI, auto-upgrades to a true
  deep-link if upstream ships it.

True per-workflow auto-open via URL is upstream-blocked
(Comfy-Org/ComfyUI#9858); tags open the editor where the curated
workflows are now pickable. Backend launch route kept (still tested).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@thinmintdev thinmintdev merged commit 66820b9 into main Jun 17, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant