RepeatImageBatch_motorway_edition

RepeatImageBatch is the "copy-paste" node for image batches. It takes an image (or a batch) and repeats it amount times, stacking the copies into one bigger batch. If you have one image and need it repeated four times because something downstream processes batches of four, this is the tool. It doesn't resize, crop, or change the pixels - it just makes more of them.

Why would you need that? Batch-oriented nodes often assume a minimum batch size, or a video frame count, or a fixed number of comparison slots. When your input is a single image and the pipeline wants four, you repeat. It's the image-side twin of RepeatLatentBatch, and it's one of those utility nodes that seems pointless until you hit exactly that wall.

On the bus

The _motorway_edition version reads from the MOTORWAY 🚌💨 bus by key:

• INPUT_image_key (default image) - the bus key holding the image batch to repeat.
• amount (default 1, range 1–4096) - how many copies to stack. At 1 it's a no-op, which is honestly the correct default for a pass-through node.
• OUTPUT_IMAGE_key (default IMAGE) - where the repeated batch is written back onto the bus.

The only return is the bus; the stacked images live inside under IMAGE. Keys are case-sensitive and shared by name - if the ramp that stored the image used a different name, change INPUT_image_key to match.

A fine point: "repeat" here means every input image is duplicated amount times in a row, so a batch of 2 repeated 3 times gives you 6 images in the order A A A B B B. If you wanted interleaved order, this isn't the node - and there isn't a stock one that does it, so plan your ordering upstream.

Install

No dependencies, no models:

cd ComfyUI/custom_nodes
git clone https://github.com/agilly1989/ComfyUI_agilly1989_motorway

or ComfyUI Manager → search ComfyUI_agilly1989_motorway → install → restart.

The fine print

The usual pack caveats apply, and they're worth repeating because they're the only real surprises here. The pack is a beta project - README opens "IF THINGS BREAK ITS BECAUSE I BROKE IT" - and the _motorway_edition clones were auto-generated by a cloner that build 1.1.7 removed, so this node may be absent from a fresh install. The stock RepeatImageBatch in core is always available and behaves identically.

Bus failure is the standard KeyError: 'hash_...' doesn't exist in motorway - the key was never stored upstream, usually a name or case mismatch. And since this node does nothing but duplicate, if something downstream is erroring after the repeat, the problem is almost certainly a batch-size assumption on the consumer side, not this node. Check the shape it's being handed before you blame the repeater.