Open ComfyUI from any device
Run ComfyUI on the machine with the graphics card and open its web interface from your laptop, over an encrypted forward that stays off until you turn it on.
Studio, powered by ComfyUI — a gallery of templates that run through Comfy-Org’s own comfy-mcp, with the full node editor one click away — is being built, and so is the MCP hub that will let agents on any of your devices drive ComfyUI. This guide covers what works today.
Install ComfyUI, or let Corewire find it
A ComfyUI already running at 127.0.0.1:8188 — the Comfy Desktop app, or one started with comfy-cli — is found on its own. To install one on the machine with the graphics card:
corewire runtimes install comfyuiCorewire prints its plan before running anything: uv tool install comfy-cli, then comfy --skip-prompt install with the flag for your graphics — --m-series on Apple silicon, --nvidia, --amd, or --cpu. It runs as you, never with administrator rights; without uv it falls back to the Comfy Desktop app through Homebrew or winget, or names the download page.
Start it
In the app, Devices › Runtimes › ComfyUI › Start runs comfy launch --background; you can also run that yourself. Once it answers:
corewire runtimesNAME STATE MODELS SHARED VERSION ADDRESScomfyui answering 0 no 0.3.66 http://127.0.0.1:8188
Let your other devices open it
In the Corewire app on that machine: Devices › Runtimes › ComfyUI › Let my other devices open its web interface. It is off by default, and it can only be switched on at that machine — never from another device.
Open it from your laptop
corewire forward mac-studio:comfyuihttp://localhost:8188 → ComfyUI on mac-studio
Open that address in a browser. The forward takes the same port when it is free, so ComfyUI behaves as if it ran here. It closes after thirty idle minutes, or when you close it:
corewire forward close mac-studio/runtime:comfyuiBare, corewire forward lists the forwards open here and everything your devices offer.
Why it is off by default
ComfyUI’s interface and API queue any workflow on that machine’s graphics card — a wider grant than answering chat — so Corewire shares neither until you say so. The API is a separate switch, for scripts that reach ComfyUI through Corewire:
corewire runtimes share comfyui oncorewire ports publish. Drive an agent on another machine.