VAE To Any 🔽

A VAE is a loaded model object - the decoder/encoder that sits at the end of every image pipeline. Like any loaded model in ComfyUI, it's not the kind of thing you usually push through a generic socket. But ComfyUI's strict typing occasionally demands it, and this node is the one-trick answer: VAE in, the identical model out, labeled * (any). It doesn't run the VAE, doesn't load a new one, doesn't touch weights.

It's part of the ComfyUI Telegram Suite pack's converter family - one XToAny node per common type (INT, FLOAT, STRING, DICT, MODEL, CLIP, VAE, IMAGE, AUDIO, LATENT), each with its AnyToX reverse, all generated from the same template.

Why it exists

The whole converter category traces back to the pack's trigger mechanism, which accepts any type to enforce execution order. Before version 1.0.4 you had to cast a signal to ANY before feeding a trigger and convert it back afterward - the README points at the size of this category as the proof of how clunky that was. Since 1.0.4 typed signals feed triggers directly, and the changelog keeps these nodes for backward compatibility.

The legitimate modern use is narrower: a third-party node with a true * input that won't accept your typed VAE output. ComfyUI doesn't coerce types across sockets; this is the minimal cast that unblocks the connection.

How it works

A bare pass-through:

def convert(self, VAE):
    return (VAE,)

Same object in and out - no decode, no encode, no memory duplication. The VAE input is a forceInput socket (wire in your VAE Loader), and the output any is type *.

Inputs and outputs

• VAE (required) - the VAE to pass through.
• any (output, type *) - the same VAE, typed as any.

Installation

Pack-wide:

cd ComfyUI/custom_nodes
git clone https://github.com/SwissCore92/comfyui-telegram-suite.git
cd comfyui-telegram-suite
pip install -r requirements.txt

or install "ComfyUI Telegram Suite" via ComfyUI Manager and restart.

Notes

If you found this node in a trigger chain from an older workflow, it's harmless and still works - it's just not required anymore. For new graphs, try wiring your VAE straight into the wildcard input first and only add the cast if the socket refuses. This node is a type-system bridge, not a workflow feature on its own.