RB Float Bridge

The most-tweaked knobs in ComfyUI are floats: denoise, CFG, LoRA strength, ControlNet weight. And they're exactly the knobs you usually can't set correctly until you've seen what the run is doing. Queue a two-stage workflow where the second pass denoises at 0.5 and you'd swear, after the first pass lands, that it should be 0.35 - and your only options are letting it run wrong or killing it and redoing the cheap first stage too.

RB Float Bridge is the in-between. Execution parks, a number box opens on the node, you type 0.35, click Continue, and only the tail runs with the corrected value. The first stage's output stays exactly as computed.

It's the float member of the pause-and-edit family in itribs/comfyui-rb-bridge, and of the four bridge types this is the one people reach for most in practice - float weights are where "let me see it first" instinct lives. (Whole numbers like steps and seed are RB Int Bridge's job.)

The inputs that matter

• value_edit (FLOAT, default 0) - the box you edit while parked. Its step is fine (five decimal places) because denoise and strength nudges are small, precise movements.
• value (FLOAT, optional) - wire an upstream float in and it becomes the value you're deciding about, loaded into the box when the pause fires. Leave it unconnected and the widget's own value is the answer.
• timeout (FLOAT) - pack-wide control: -1 waits for you (default), 0 skips the pause and passes through instantly, >0 auto-continues after N seconds.

Output is a single value (FLOAT). It plugs into any float-consuming input downstream - a sampler's denoise, a LoRA loader's strength, a ControlNet's weight.

How it works

Same engine as the rest of the pack: the node sends a session event to the frontend, your Continue and Cancel buttons enable, and a server-side wait loop blocks the run until you answer. Continue posts the box's value back over an HTTP route and the node returns it; Cancel interrupts the whole workflow. The loop polls for interrupts every tenth of a second, so the ordinary Stop button still gets you out of a parked run.

Because the input is a float with a fine step, this is the bridge where you'll most feel the timing: the pause happens mid-run, the box is already showing the value that reached it, and one small correction changes everything downstream. Set timeout to 0 and no wire, and it stops pausing - it just passes value_edit through, making it a plain typed float source (ComfyUI's PrimitiveFloat equivalent) when you don't need the interactivity.

Where it hurts if you misuse it

ComfyUI caches work whose inputs haven't changed, and these bridge nodes don't force re-execution the way RB Pause's force_pause does. Re-queue an untouched workflow and the node can be skipped - no pause. If it sails past, change the value_edit widget or anything upstream and it'll park again. And remember timeout at -1 waits on you forever; that's the design, but don't stack queued jobs behind a pause you won't be at the keyboard for.

Installation

One repo installs all five nodes, with zero external dependencies and no model downloads. Via ComfyUI Manager, search comfyui-rb-bridge, or:

cd ComfyUI/custom_nodes
git clone https://github.com/itribs/comfyui-rb-bridge

Restart ComfyUI, then hard-refresh the browser tab - the number box and buttons are frontend elements, and a stale tab is the usual reason they don't render. Find the node by searching "RB" under the bridge category.

Common issues

• It just hangs at timeout -1 - that's the point. Continue to resume; Stop also unblocks it.
• Buttons missing or misrendered. The pack draws its own DOM widgets on the classic canvas; under ComfyUI's newer Nodes 2.0 rendering, widget-heavy custom nodes have been known to break (rgthree's included). Flip back to the classic canvas before hunting deeper.
• Cancel stops everything, not just the tail. Only Continue preserves the run.