PS Batch

The name is doing more work than the node. PS Batch does not batch anything. It does not duplicate your image, and it does not queue extra runs. It outputs a single integer, 1 through 4, and you wire that integer where the count is supposed to come from.

Which is the correct design, honestly. Somebody in Photoshop needs a "how many" control, that control has to survive a trip across the bridge as a real integer, and ComfyUI needs to be able to consume it as an INT. A three-line value node is all that takes.

How it works

One widget, one output. The widget is value - an INT with defaults of 1, minimum 1, maximum 4 and a step of 1, defaulting to 1. The output is named count, which is a slightly annoying naming mismatch, and that's the whole schema. For it to do anything you connect count to a node that actually uses a batch size: RepeatImageBatch, an empty-latent node's batch size, any latent batch input.

The interesting part is what happens the other way. Vplugins runs workflows through the local HTTP API, and ComfyUI's core is famously relaxed about API input types - hand it "2" or 2.7 and it'll happily coerce to an int for you. This pack doesn't want that, because a batch count is one of the parameters Photoshop lets a user edit and a silently coerced value is a bug you'll find three steps later. So the value is validated three separate times: on the node itself, in the parameter patch/manifest path, and in the pack's own middleware for direct raw /prompt submissions. Hand it a float or a numeric string and you get a rejection, not a quiet 2.

Cost note: the Bridge budgets results per run as batch count × the number of Send to PS nodes, under a global cap of 64 results. Batch 4 and three output nodes is twelve finished PNGs from one click, which is fine - just don't stack batches expecting the cap to be somebody else's problem.

Two structural rules, both enforced by the graph check: it's socketless (nothing can be wired into value; you set it or Photoshop sets it) and there's one PS Batch per workflow.

Inputs and outputs

• value - INT, 1–4, default 1.
• count - INT output. Wire it to a batch-size input.

That's the list. There are no advanced fields.

Install

ComfyUI Manager → ComfyUI PS Bridge Nodes, or:

cd ComfyUI/custom_nodes
git clone https://github.com/AIGCTV/comfyui-ps-bridge-nodes.git
cd comfyui-ps-bridge-nodes
python -m pip install -r requirements.txt

Restart ComfyUI and hard-refresh the browser; nodes land under Add Node → 🔷PS Vplugins. Two light dependencies, no models. Needs a ComfyUI with the V3 node API, classic canvas recommended.

Troubleshooting

"I set it to 3 and got one image." It only outputs a number - the count has to reach something that repeats. In the bundled PS_Bridge_Roundtrip.json that something is RepeatImageBatch. Nothing wired to count means nothing batched.

"The value won't take what I typed." Non-integers are rejected by design (see above). Set it in the widget, or send it an integer through the bridge.

You want a batch bigger than 4. Not here. Wire a separate INT primitive in parallel and use that for the local workflow; the 1–4 range exists because it's what the Photoshop-side control offers.

Second PS Batch node added. The graph is rejected - one per workflow, same as PS Seed, PS Slider and PS Prompt.