Bug Description

The default_launch_extras configuration setting in config.ini is not being applied when running comfy launch without additional arguments. Despite being properly set in the configuration file, ComfyUI launches with default settings instead of the configured launch extras.

Environment

• OS: Windows 11 (Platform: win32)
• Python Version: 3.12.10
• comfy-cli Version: 1.4.1
• ComfyUI Version: 0.3.49
• Installation Method: pip

Steps to Reproduce

1. Set default launch extras using the documented method:

   comfy set-default . --launch-extras="--listen 0.0.0.0 --port 8000"

2. Verify the configuration was saved correctly in %LOCALAPPDATA%\comfy-cli\config.ini:

   [DEFAULT]
   enable_tracking = False
   recent_workspace = C:\ComfyUI
   default_workspace = C:\ComfyUI
   default_launch_extras = --listen 0.0.0.0 --port 8000

3. Launch ComfyUI using:

   comfy launch

Expected Behavior

ComfyUI should launch with the configured launch extras, listening on 0.0.0.0:8000 as specified in default_launch_extras.

Actual Behavior

ComfyUI launches with default settings, showing:

To see the GUI go to: http://127.0.0.1:8188

The configured --listen 0.0.0.0 --port 8000 arguments are ignored.

Workaround

The launch extras work correctly when specified explicitly:

comfy launch -- --listen 0.0.0.0 --port 8000

This correctly shows:

To see the GUI go to: http://0.0.0.0:8000

Additional Information

• The comfy set-default command successfully updates the config.ini file
• The configuration file is located at: C:\Users\ProArt\AppData\Local\comfy-cli\config.ini
• Both quoted and unquoted values for default_launch_extras were tested with the same result
• No error messages are displayed; the setting is simply ignored

Possible Root Cause

It appears that the comfy launch command is not reading or applying the default_launch_extras configuration value from the config.ini file, despite the feature being documented in the README.

Impact

Users cannot set persistent default launch arguments for their ComfyUI installation, requiring them to manually specify arguments each time or create wrapper scripts.