🔄 Workflow Runner

The most fully-specified of the pack's three "Utils🛠" dev-tool nodes, and the one that gives away the most about how the author actually uses this pack day to day. It takes a path to a workflow JSON file, a port, a manual run switch, and a browser-opening toggle - put together, that's a node for launching a separate ComfyUI workflow, most likely on a second local instance given the port input, without leaving the graph you're already in.

One detail is worth calling out on its own because it's genuinely revealing about the pack: the default workflow_path is a literal Windows path - C:\ComfyUI_windev\ComfyUI\user\default\workflows\text_test.json. That was obviously never meant as a real path for you to use; it's just what happened to be on the author's own dev machine when the node shipped, folder name and all (windev - a Windows dev install). It's a small, honest tell that this pack, this trio especially, is closer to "tools I built for my own workflow-testing loop" than "polished feature aimed at general users." Worth knowing going in, not a knock on the node itself.

How it works

Give it a workflow file, a port, and flip run to true, and it's meant to launch that workflow - again, most plausibly by starting or driving a second ComfyUI instance on the specified port, then optionally opening a browser tab pointed at it. As with its two siblings in this trio, there's no description shipped and the README doesn't mention it, so this is a schema-and-category reading, not a look at the source.

The inputs and outputs that matter

• workflow_path (STRING) - point this at an actual workflow JSON on your own machine; the shipped default definitely isn't a real path anywhere but the author's box.
• port (INT, default 8188, range 8188–8199) - note this floor starts right at ComfyUI's own default port, unlike the Port Runner node's 8190 floor - double-check it won't collide with the ComfyUI instance you're already running this graph from.
• run (BOOLEAN, default false) - the manual trigger. Leave it false while you set the path and port, flip it to true when you actually want it to fire; this also plays well with ComfyUI's execution caching, since nothing happens again on a re-run unless something upstream - including this toggle - actually changed.
• open_browser (BOOLEAN, default true) - whether it opens a browser tab pointed at the launched instance once it's up.
• The output - plain STRING in the schema - most likely reports status.

How to install it

Standard pack install. ComfyUI Manager: search ComfyUI Neural Nodes, install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/xobiomesh/ComfyUI_xObiomesh

then restart. No models involved, nothing heavy to fetch.

Common issues & troubleshooting

Nothing happens when you expect it to. Check run is actually set to true - it defaults to false specifically so the node doesn't fire just by existing in your graph, and it's an easy field to forget to flip.

Path error, or it silently does nothing with the default settings. The default workflow_path is a Windows path from the author's own machine, not a placeholder that resolves anywhere else - you have to replace it with a real path on your system before this node can do anything useful.

Port collision. If you're already running ComfyUI on 8188 - the field's own default - and try to launch a second instance on the same port, expect it to fail to bind. Nudge the port up into the 8189+ range instead.

Same caution as this trio's other two nodes: this launches an external process on your machine, the same arbitrary-execution surface every custom node has by default, just aimed more explicitly than most. Know what workflow file you're actually pointing it at before you flip run.