快速运行中控台

Here's the workflow-debugging pain this solves: you've got a 60-node monster - some API calls, some local prep - and you want to re-run just the "build the reference images" group without paying to re-call every cloud model in the graph. Stock ComfyUI makes you either run everything or manually bypass a dozen nodes. GroupRunnerConsole gives you a button per group instead: drop it on the canvas, it scans your workflow's groups, and you click the one you want to run alone.

It's a tool-only node with no inputs and no outputs (is_output_node is true - it's a control surface, not a data pass-through). That makes it a debugging sidekick for the whole pack, which is handy here because every generative node in ComfyUI-nkxx is a paid cloud call. Re-running an entire multi-model workflow because you want to tweak one group is how you burn a day's credits on accident. This node is the antidote.

How it works

The logic lives in the frontend (web/tools.js). On creation it scans app.graph._groups, lists every group's title, and draws a button per group inside the node. Click a button and it runs that group in isolation. The Python side is essentially a stub - which is why it has no sockets at all. It also self-sizes: the taller your list of groups, the taller the node grows, and it enforces a minimum size so it never squishes into unreadability.

There's a subtle ComfyUI-ecosystem framing worth knowing: this is the same "run a sub-graph in isolation" problem that dedicated tools like rgthree's group reroute or bypass systems tackle in their own ways. This one is dead simple - a button list, no reroute plumbing, no config. Simple is good for a debug console; you want zero friction between "I want to test this group" and "it's running."

Using it

Nothing to configure. Add it to the canvas, wait a moment for the scan, and the group buttons appear. A couple of practical notes:

• Groups are matched by title, so renaming a group after the console scanned it may leave a stale button - rescan by toggling the node or reloading the workflow.
• It runs the selected group only. If that group depends on something produced upstream, you'll need that upstream group run first - the console doesn't resolve dependencies for you. Use it for self-contained groups (a prompt-builder block, an image-prep block), not for the middle of a chain.
• In this pack, the obvious use is isolating the free/local prep groups from the paid API groups. Verify your local prep group works before you spend a single API credit, then wire up the calls.

Install

Same pack, one install: ComfyUI Manager (search "ComfyUI-nkxx"), or

cd ComfyUI/custom_nodes
git clone https://github.com/jieg9341-lab/ComfyUI-nkxx

then restart. It pulls in nothing beyond the pack's standard auto-installed deps (requests, pandas, aiohttp, yt-dlp, opencv-python, openpyxl), and there are no models to fetch - the whole pack is cloud-API wrappers, so the "heavy dependency" list here is just those six pip packages.

If the group buttons don't show up after you add it, that's the classic frontend-extension timing issue: reload the page once, and if it still won't list groups, restart ComfyUI. It's a JS widget, so a stale extension cache is the usual culprit, not your workflow.