🚀 ComfyUI Port Runner

This one's a real departure from the rest of the pack. It's not an image node, a text node, or an LLM node - it's infrastructure. Judging by its name, its single input, and where it sits in the pack's category tree (grouped under a wrench-icon "Utils🛠" folder alongside the Test Script Runner and Workflow Runner, separate from the plain-Utils file and text nodes), this looks like a dev-tool the author built for managing or launching a second ComfyUI process on a specific port, from a node running inside a first ComfyUI process.

Be upfront about what this reading is and isn't: the node ships with no description text, and it's not mentioned anywhere in the pack's README - which only documents two of the pack's eight nodes, both unrelated to this one. Everything below is inference from the schema and the category it's filed under, not a read of the source. Treat it as a starting point, not a spec.

How it works

There's not much to go on beyond the input/output shape: one INT in (port), one STRING out. The most reasonable interpretation is that this either starts, stops, or checks a ComfyUI process listening on the given port and reports back a status or URL string.

The inputs and outputs that matter

• port - an INT, default 8190, constrained to a narrow range of 8190–8199. That range is a genuine clue: ComfyUI's own default port is 8188, so this node's floor sits two above it - almost certainly deliberate, to avoid the node colliding with the ComfyUI instance you're already running the graph from.
• The single output - labeled just STRING in the schema, no friendlier name given - 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. Pure orchestration, no models to fetch.

Common issues & troubleshooting

There's no community track record to draw on here - searching for this pack turns up nothing anywhere, so there's no crowd-sourced list of known issues to hand you. A few things worth knowing before you wire it in regardless:

This is not something most workflows need. If you're not doing what the pack's own dev-tool trio implies the author was doing - running or testing a second local ComfyUI instance from within a graph - there's little reason for this node to be in your workflow at all.

Know what it actually does before you run it. Any custom node that starts or manages another process is running arbitrary Python with your full user permissions the moment it loads - that's true of every node in this ecosystem, not just this one, because ComfyUI has no sandboxing for custom nodes at all. A node explicitly built to spawn or control a process is that same lack of sandboxing pointed at something more direct than usual. Nothing here suggests bad intent - it reads like a genuine personal dev-testing convenience the author shipped along with the rest of the pack - but it's worth knowing what a "port runner" is going to do before you hit go, the same way you would for any node that shells out to something.