Exactly Bright Pulse

Exactly Bright Pulse is a hosted, reference-driven photo model, and the first thing you'll notice is what's missing: there's no prompt box. The entire input contract is reference images plus a canvas size. You feed it pictures that establish the subject and the look, and the model carries that identity into a fresh generation. That's the whole trick, and for style-consistency work it's refreshing - no prompt-balancing act, no negative-prompt choreography, just "here's the vibe, make more like it."

The name is the aesthetic pitch: bright, high-key, luminous. If the look you want is punchy daylight and clean highlights, this is the variant in the Exactly photo family to reach for - the siblings split on contrast and warmth, and Bright Pulse sits firmly on the bright side.

What you set

• referenceImages (required) - wired from the Runware Reference Images builder. That's where you actually work: each reference carries a type (its purpose), a tag like @actor1 that links it to a mention, and the image itself. One or several; more refs means more consistent identity transfer.
• width / height - the output canvas, default 1024×1024.
• numberResults - up to 20 variations, each on its own seed. This is the iteration knob.
• watermark - optional builder output if you need one stamped in.
• outputFormat - JPG / PNG / WEBP, plus outputQuality (20–99).

Output is image (IMAGE), ready for Preview Image or Save Image.

How it works

Mechanically it's the standard pack flow: build a request with the Exactly Bright Pulse model AIR and taskType: imageInference, send it over REST via the SDK, download the result as a native IMAGE. Your reference images are encoded and shipped with the request; the model runs in the cloud and the title bar reports the cost. The reason to use this over prompting a local checkpoint from scratch is consistency - the reference contract does the heavy lifting that tags and CFG wrestling would do locally.

Installing

ComfyUI Manager → search Runware → install → restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/Runware/ComfyUI-Runware
pip install -r ComfyUI-Runware/requirements.txt

No model downloads; deps are runware-sdk, pillow, soundfile. API key via Settings → Runware API key, RUNWARE_API_KEY, or runware auth login.

Troubleshooting

If results drift from your references, check the builder, not the model: references need a type and a tag, and a tag mismatch is the classic cause of identity loss. A missing or empty reference socket also means the job has nothing to hold onto - the socket is required for a reason. Want the same pipeline but punchier blacks? That's Exactly Extreme Contrast, the sibling that flips the tonal balance.