StackPushFloat

StackPushFloat saves a decimal number to a stack on disk so a later workflow can read it back with StackPopFloat. It's the float twin of StackPushInt, and the distinction matters: integers are your widths, heights, and seeds; floats are your dials - CFG scale, denoise strength, LoRA weight. The knobs you tweak to steer a generation.

In a split pipeline - workflow A renders, workflow B processes - this is how B learns the exact CFG and denoise A used, so it can reproduce or refine the result instead of guessing. Same pattern as the int node: push with key cfg, pop with key cfg on the other side. The values stay in sync because one workflow produced them and the other just reads them.

Two inputs to know:

• numbervalue - the decimal to save (e.g. 7.5).
• key - the stack's name, default "default". Must match on the pop side, capitalization included.

stackpath defaults to ./ComfyUI/Stack/ under your ComfyUI install and can be left alone.

How it works

As mechanical as it gets: the value is written as text into a timestamped ._fl file in ComfyUI/Stack/<key>/. The timestamp gives files their order, which is what makes "newest = top of stack" work on the pop side. Open the file and you'll see your number as plain text, so nothing is opaque here. And because the stack lives on disk, the value survives ComfyUI restarts - in-memory handoffs don't.

One behavior to know: the node always executes when the queue reaches it, even if the value didn't change. Deliberate, so the other workflow always sees current data.

Install

Same as every node in this pack:

cd ComfyUI/custom_nodes
git clone https://github.com/concarne000/ComfyUI-Stacker

then restart ComfyUI (or find "ComfyUI-Stacker" in ComfyUI Manager). No models to download, and the only listed dependency is pickle, which is Python's standard library - so there's nothing to resolve or fight about.

Gotchas

• Keys are case-sensitive and must match the pop node. "CFG" and "cfg" are separate stacks.
• The stack path is relative to where ComfyUI launches from. Odd launch directory, odd stack location.
• Pushing is safe and non-destructive; popping isn't. StackPopFloat deletes the file after reading by default, so for a value you want available on every run, push it fresh or pop with Peek.