FLOAT Literal

This is about as simple as ComfyUI nodes get: one float value in, the same float value out. No transformation, no logic - it's a named source you can point at a number once and wire to as many downstream nodes as you want.

Why bother with a dedicated node for that? Because plenty of ComfyUI's built-in widgets are welded to a single node - a KSampler's denoise slider, say, or a LoRA loader's strength value - and there's no native way to share one number across two of them without either duplicating the value by hand (and having it silently drift when you tweak one but forget the other) or right-click → "convert widget to input" and wiring something upstream into it. A FLOAT Literal is that upstream something: set the number once, wire it to every node that needs it, and you now only ever have one place to change it. A shared denoise value across two chained samplers, or a CFG you want visible in one obvious spot on a busy graph, are both exactly this pattern.

Mechanism. Nothing more than a stored float, output as-is. It exists purely as plumbing.

Inputs and outputs. One required input, value - a FLOAT, default 0 - and one output, also typed FLOAT and simply named "FLOAT." That's the entire node.

Installing it. Comes bundled in TW-CUI-Util, a small ComfyUI utility pack built around exactly this kind of consolidation. Grab it through ComfyUI Manager - search "TW-CUI-Util", install, restart - or manually with git clone https://github.com/TW-CUI/TW-CUI-Util into ComfyUI/custom_nodes, then restart. No dependencies, no models - it's a handful of lines of Python.

Troubleshooting. There's genuinely very little that can go wrong with a node this small. One thing worth flagging: this is a plain float with no min/max/step configured, unlike a proper widget for CFG or LoRA strength that usually clamps to a sensible range - so if you're using it to drive something like cfg on a KSampler, ComfyUI won't stop you from typing in a value that's nonsensical for that field, because the literal itself has no idea what it's feeding. Sanity-check the number against whatever's downstream rather than trusting the node to guard the range for you.

If you're used to ComfyUI's own native Primitive node - the generic one that auto-detects its type from whatever it's wired to - this is functionally similar, just explicitly float-typed instead of generic. That mostly matters for readability: glance at a crowded graph and you know at a sight this particular box can only ever hold a decimal number, instead of tracing a wire to find out.

If a node like this vanishes from your search box after an update, that's a "the pack failed to import" problem rather than anything specific to this node - check your ComfyUI startup console for an error mentioning TW-CUI-Util before assuming you've lost the node for good.