default_launch_extras configuration not being applied when using 'comfy launch'

[wangkanai]

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.

[dosubot]

Hi @wangkanai! I'm Dosu and I’m helping the comfy-cli team.

This is a known edge case in comfy-cli: the code is designed to apply default_launch_extras from config.ini when running comfy launch without extra arguments and with the default workspace, but due to how CLI arguments are parsed, the setting can be ignored if the extras argument is present as an empty list (e.g., ['']). This means the config value is not applied unless you explicitly pass launch extras on the command line, which matches your workaround. The splitting logic for extras is also quite basic and may not handle complex or quoted arguments well. The documentation does not clarify this behavior, but the code shows it is intended to work as you expect (source).

For now, specifying launch extras explicitly after -- is the reliable workaround. It would be helpful for maintainers to clarify or fix this behavior in future releases.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[beyandbey]

Hi,
I encountered very similar behavior, but believe the issue has a different root than that pointed out by @dosu-bot. Did you by any chance run comfy launch from the same directory as your default workspace? That's what caused the issue for me. Changing to a different directory before launching fixed this.

Reconstructing how this issue arises, I found that the launch function only applies default launch extras if the workspace type matches the default workspace.
However, when launched from the same directory, the workspace_manager recognizes the workspace to be WorkspaceType.CURRENT_DIR rather than WorkspaceType.DEFAULT_DIR, despite resolving to the same path.

Immediate fix:

• change to different directory before launching

(Probably) Permanent Fix:

• Also check whether current_dir matches default_dir when determining whether to apply default launch args.