Open Web

Most of ComfyUI is about producing something inside the graph - an image, a string, a file on disk. Open Web does something different: it's a deliberate side effect. Run this node, and it opens path_or_url in whatever your OS treats as the default handler for it - a browser for a URL, the associated app for a local file. It's the pack's way of letting a workflow reach outside itself when it finishes: pop open a generated report, launch a reference page, open a rendered file automatically instead of you hunting for it in a folder.

The default value in path_or_url is, charmingly, a link back to the pack's own GitHub repo - swap it for something you actually want opened.

How it works

This is deterministic, not agent-driven: you set path_or_url yourself, on the node, and it runs every time the node executes. If you want an LLM deciding on its own when and what to open, that's a different node in this same pack, open_url_tool - this one always does exactly what you told it to.

The inputs and outputs that matter

• path_or_url (default the pack's own GitHub URL) - what to open. Required.
• is_enable - the pack's standard bypass toggle.

One output: log (STRING) - a status string reporting what happened. is_output_node: true, so it'll run and produce that log even with nothing wired downstream of it.

How to install it

• ComfyUI Manager: search "comfyui_LLM_party", install, restart.
• Manual: cd ComfyUI/custom_nodes && git clone https://github.com/heshengtao/comfyui_LLM_party, then pip install -r requirements.txt from inside the pack folder using ComfyUI's own Python, then restart.

No dependency of its own beyond the base pack - it's a thin wrapper around your OS's own "open this" call.

Common issues & troubleshooting

Nothing visibly happens. This node only makes sense on a machine with a real desktop and a default browser to open into. If ComfyUI is running headless on a remote GPU worker or a cloud executor - which is exactly how most serverless ComfyUI platforms run - there's no display for a browser to appear on, so the "open" step either fails quietly or errors depending on how the underlying OS call behaves. Treat this as a local-desktop convenience node, not something to build a remote or cloud workflow around.

A local file path doesn't open. Confirm the path is one the ComfyUI process can actually see - if you're running ComfyUI inside a container or on a different machine than the one you're browsing from, a path that makes sense on your laptop may not exist on the machine actually executing the node.

log reports success but you don't see anything. That usually just confirms the OS-level open call was issued - whether anything visibly appears still depends on whether there's a display session for it to appear in, which is outside this node's control.