[GH-ISSUE #1734] [Feature Request]: Outside facing Open port for remote access to Main Desktop application #531

New issue

Open

opened 2026-10-31 22:14:08 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 22:14:08 +00:00

Owner

Originally created by @DevNullInc on GitHub (Jun 7, 2026).
Original GitHub issue: https://github.com/Comfy-Org/desktop/issues/1734

Prerequisites

I have searched the existing issues and checked the recent builds/commits
I have read the documentation and this feature is not already available
This is a single feature request (not multiple features combined)

Problem Statement

The current desktop application architecture encapsulates the underlying server instance within the Electron container without exposing a configurable network listening port to the host machine.

Key limitations with this architecture:

Restricted Interface Access: This implementation restricts user interaction entirely to the native window shell, preventing the interface from being accessed or managed via standard external web browsers.
Blocked Tunneling Integration: The absence of a dedicated listening port blocks integration with local network orchestration tools and tunnel daemons, such as Cloudflared, which require a predictable local port binding to manage reverse-proxy routing.

Proposed Solution

Introduce a configuration setting or a command-line startup flag (e.g., -port) that enables the desktop client to expose and bind its internal server components to a user-defined port on the host machine.

Expected Outcome:

Decoupled Frontend Rendering: Users will be able to interface with the container directly using standard web browsers instead of being locked into the Electron window shell.
Seamless Local Proxy Routing: Exposing a predictable local port will allow local daemon services like Cloudflared to hook into the interface natively, enabling clean subdomain routing without altering the core desktop security baseline.

Potential workflow

Launch the ComfyUI desktop application via the CLI or terminal utilizing a specific port flag (e.g., comfyui-desktop --port 8000) or configure a persistent host port binding within the desktop application configuration file/settings panel.
The desktop application initializes its internal container and successfully binds the web interface to the designated local port on the host machine.
Open a standard external web browser and navigate to http://localhost:8000 (Or whatever port is chosesn) to access and manage the full container workspace directly.
Alternatively, point a local Cloudflared tunnel daemon at the exposed local port to securely map the instance interface to a custom domain (such as comfy.websitehere.net) for seamless proxy routing.

Impact Level

High (Major improvement)

Alternatives Considered

CLI-Only Deployments: Running the pure, standalone command-line version of ComfyUI natively allows port and host binding, which works perfectly for browser access and tunneling. However, opting for this approach bypasses the standalone desktop manager wrapper entirely, forfeiting the streamlined instance management, updates, and integrated desktop environment features that the new desktop application container provides.
Manual Port Proxying: Attempting to force-route internal Electron window traffic via external network monitoring hooks or severe OS-level loopback workarounds, which is overly complex, fragile, and completely unnecessary when a simple configuration flag can native-bind the port.

Additional information

I use Cloudflared tunnels quite often for a lot of my work as it allows my high powered desktop to stay at home where I can then access all my services from either my phone, tablet or my galaxy book,chromebook laptop when remote and this would be a huge QOL upgrade for me and probably quite a few other people.

Originally created by @DevNullInc on GitHub (Jun 7, 2026). Original GitHub issue: https://github.com/Comfy-Org/desktop/issues/1734 ### Prerequisites - [x] I have searched the existing issues and checked the recent builds/commits - [x] I have read the documentation and this feature is not already available - [x] This is a single feature request (not multiple features combined) ### Problem Statement The current desktop application architecture encapsulates the underlying server instance within the Electron container without exposing a configurable network listening port to the host machine. **Key limitations with this architecture:** * **Restricted Interface Access:** This implementation restricts user interaction entirely to the native window shell, preventing the interface from being accessed or managed via standard external web browsers. * **Blocked Tunneling Integration:** The absence of a dedicated listening port blocks integration with local network orchestration tools and tunnel daemons, such as Cloudflared, which require a predictable local port binding to manage reverse-proxy routing. ### Proposed Solution Introduce a configuration setting or a command-line startup flag (e.g., `-port`) that enables the desktop client to expose and bind its internal server components to a user-defined port on the host machine. **Expected Outcome:** * **Decoupled Frontend Rendering:** Users will be able to interface with the container directly using standard web browsers instead of being locked into the Electron window shell. * **Seamless Local Proxy Routing:** Exposing a predictable local port will allow local daemon services like Cloudflared to hook into the interface natively, enabling clean subdomain routing without altering the core desktop security baseline. ### Potential workflow 1. Launch the ComfyUI desktop application via the CLI or terminal utilizing a specific port flag (e.g., `comfyui-desktop --port 8000`) or configure a persistent host port binding within the desktop application configuration file/settings panel. 2. The desktop application initializes its internal container and successfully binds the web interface to the designated local port on the host machine. 3. Open a standard external web browser and navigate to `http://localhost:8000` (Or whatever port is chosesn) to access and manage the full container workspace directly. 4. Alternatively, point a local Cloudflared tunnel daemon at the exposed local port to securely map the instance interface to a custom domain (such as `comfy.websitehere.net`) for seamless proxy routing. ### Impact Level High (Major improvement) ### Alternatives Considered * **CLI-Only Deployments:** Running the pure, standalone command-line version of ComfyUI natively allows port and host binding, which works perfectly for browser access and tunneling. However, opting for this approach bypasses the standalone desktop manager wrapper entirely, forfeiting the streamlined instance management, updates, and integrated desktop environment features that the new desktop application container provides. * **Manual Port Proxying:** Attempting to force-route internal Electron window traffic via external network monitoring hooks or severe OS-level loopback workarounds, which is overly complex, fragile, and completely unnecessary when a simple configuration flag can native-bind the port. ### Additional information I use Cloudflared tunnels quite often for a lot of my work as it allows my high powered desktop to stay at home where I can then access all my services from either my phone, tablet or my galaxy book,chromebook laptop when remote and this would be a huge QOL upgrade for me and probably quite a few other people.

bsakaguchi added the

enhancement

label

2026-10-31 22:14:08 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Comfy-Org/desktop#531

No description provided.

Rows
Columns