Recall Float

Recall Float reads back a floating-point number your Cyclist loop stored on a previous run. It's the partner to Memorize Float, and it's the node that lets a loop compare against its own history - most often a quality score, which is how "keep regenerating until it's actually good" loops work.

The pattern it drives

ComfyUI has no loops, so Cyclist re-queues the whole workflow, one iteration per Queue Prompt, and nothing survives the gap on its own. Recall Float is the survival. The textbook example from the pack: generate an image, score it with something like ComfyUI-ImageReward, and Memorize Float the score. Next run, Recall Float brings that score back, Compare Anything checks it against your target, and if it clears the bar an Interrupt node stops the loop. The float you recall is the memory that makes the stop condition meaningful - without it, every run would be judging in a vacuum.

The fallback matters here more than it looks. On iteration one there's no stored score yet, so Recall Float hands back the fallback. Set that to a value that guarantees the loop keeps going on the first pass (a deliberately low or high number, depending on your comparison), and you avoid an accidental instant-stop.

The inputs that matter

• loop_id (STRING, default ForLoop_1) - the slot to read. Match it to the Memorize Float that wrote the value.
• fallback (FLOAT, optional, default 1) - returned when nothing's memorized yet. This is your first-iteration seed value; pick it so the loop behaves on pass one.

Output is one FLOAT - wire it into a comparison, a math node, a denoise/CFG input, wherever a decimal is needed.

Install

• ComfyUI Manager: search comfyui-cyclist, install, restart.
• Manual: cd ComfyUI/custom_nodes && git clone https://github.com/Pos13/comfyui-cyclist, restart.

No models or wheels - pure Python.

Gotchas

Memory is RAM-only, so restarting ComfyUI wipes it and Recall Float drops to its fallback. For an in-session "generate until good" loop that's exactly right; for anything you need to keep across restarts, Cyclist's disk nodes handle images/latents/models, not raw floats.

The comparison-chain snag worth flagging: some scoring nodes from other packs (WAS Node Suite comes up a lot) only speak in number-form booleans, so you occasionally need Cyclist's Convert to node to bridge a boolean into a float before the math works. That's a quirk of those neighbours, not of Recall Float, but it's where these score loops tend to catch.

And the pack-wide note: Cyclist is archived and the author isn't maintaining it. Works now, no future support.