Conductor Test

Drag "Conductor Test" onto the canvas and you'll stare at it for a moment. There are no widgets to touch, no sockets on either side, nothing happens when you queue. That's not you missing something - the node genuinely does nothing, and it's honest about it. Its own description calls it "a minimal Conductor Node 2.0 integration test." This is the canary, not the coal mine.

What Conductor is supposed to become

The parent pack, Marauberry/ComfyUI-Conductor, is pitched hard: "The workflow control center for modern ComfyUI. Build once. Switch anything." A single node that fronts your whole workflow so you swap models, prompts, and settings from one clean surface instead of spelunking through a fifty-node graph. That's the dream the README is selling.

Reality check: the repo is version 0.1.0, and its entire node inventory is this test node. There is no control center here yet, and no community footprint at all - nothing on the usual forums as of this writing. If you installed this expecting "build once, switch anything" today, you'd be installing a promise. Keep an eye on it if the pitch appeals to you, but don't clear out your rgthree context nodes for it.

How it actually works (and why it's interesting)

The genuinely useful thing about Conductor Test is what its source looks like. Open nodes/conductor_test.py and you'll find a node written against ComfyUI's newer backend authoring API, the V3 schema - from comfy_api.latest import ComfyExtension, io, a class subclassing io.ComfyNode, a define_schema() classmethod that declares the node, and registration through an async comfy_entrypoint() whose get_node_list() returns the extension's nodes. No NODE_CLASS_MAPPINGS dict in sight.

That's the modern style ComfyUI is moving its own core nodes onto, and it coexists with the classic registration you see in 99% of older packs. Conductor Test is a clean, minimal example of it: define_schema() returns an io.Schema with a display name, a category ("Conductor"), a description, and empty inputs and outputs, and execute() returns an empty io.NodeOutput. That's the entire node. What it proves is that the whole extension pipeline - package entrypoint, extension object, schema declaration - loads end to end. If you see "Conductor Test" in the node menu under Conductor, the pack's plumbing works.

Inputs and outputs

There are none, and that's the point. Zero inputs, zero outputs, not flagged as an output node. Place it in a workflow and it contributes nothing to the graph and reads nothing from it - it's a load test for the author, and a teaching artifact for you.

Installing it

The README gives you no install instructions at all, so use the standard route. In ComfyUI Manager, search the pack title "comfyui-conductor" and install, or:

cd ComfyUI/custom_nodes
git clone https://github.com/Marauberry/ComfyUI-Conductor

then restart ComfyUI. There's no requirements.txt, no model downloads, no heavy deps - the only real dependency is comfy_api, which your ComfyUI ships itself.

The one gotcha

Because it imports comfy_api.latest, this needs a recent ComfyUI build that includes the V3-schema backend. On an older install the import fails at startup, the pack silently doesn't load, and "Conductor Test" won't appear in the menu - which, ironically, means the test node did its job by failing. Update ComfyUI and try again. That's about the only failure mode there is, because there's nothing else for it to get wrong.