Icy ConditioningConcat

IcyConditioningConcat is the IcyHider clone of ConditioningConcat, and it's the easiest node in ComfyUI to confuse with its cousin ConditioningCombine - so let's settle that in the first paragraph. Combine says "use both." Concat says "treat these as one prompt." They look alike, they output the same type, and they behave very differently.

What it does

Two inputs, one output:

• conditioning_to - the base conditioning (its tokens come first).
• conditioning_from - the conditioning whose tokens get appended (its tokens come second).
• Output: a single CONDITIONING where the second prompt's token embeddings are glued onto the end of the first's, forming one longer embedding sequence.

Mechanically that's the key difference from Combine: instead of running two independent conditionings, Concat literally concatenates the embedding tensors along the token dimension. The model reads the result as one continuous prompt. Because the token sequence is longer, it also has the side effect of stretching past the 77-token ceiling - a reason people reach for it when one encode alone truncates.

When to use it

• A style suffix that shouldn't fight the subject. Concat a "mood/style" prompt onto a "subject" prompt and the subject tokens keep priority (they come first), with the style read as context. That ordering matters - put what you care most about in conditioning_to.
• Pushing past the token limit. Two encodes of ~70 tokens each concatenated give you a longer effective prompt than either alone.
• Compositional prompting. Build a prompt from parts the same way you'd chain words in a sentence.

The trap is thinking it's interchangeable with Combine. They're not: Combine keeps two independent conditionings (each with its own metadata - regions, areas, ControlNet edits); Concat flattens everything into one sequence and drops the per-conditioning metadata. If you concat two region conditionings, the region areas are lost. Use Combine for anything with regions or separate strengths; use Concat when you genuinely want one long prompt.

The "Icy" caveat

Outputs CONDITIONING - no preview for IcyHider to hide, so the wrapper is cosmetic. It's the pack's automatic clone of every core node; ConditioningConcat is the exact code underneath.

Install

ComfyUI Manager → search "IcyHider" → install → restart, or:

cd ComfyUI/custom_nodes
git clone https://github.com/icekiub-ai/ComfyUI-IcyHider.git

Restart. No Python deps, no models bundled. Node under IcyHider Comfy Core. And when a workflow you downloaded uses this node, read it as a deliberate "one long prompt" choice - the author meant to flatten the two branches.