T

In a pack with 106 nodes, the one called just "T" doesn't look like much. It isn't. It's a single boolean - True or False - passed through from input to output. What makes it worth having is the UI: the pack replaces the plain checkbox with a proper little toggle switch on the canvas, so you can flip a setting with one click instead of clicking into a primitive's dropdown.

This is the UI-utility tier of CRT-Nodes (the same family as the "K" knob node). These nodes add no generation capability at all - their entire job is keeping a big workflow comfortable to drive. That's a real job, by the way: the custom-node ecosystem's most-loved utility packs exist precisely because sprawling graphs become unmanageable without things like this.

What it does

One input, one output:

• value - a BOOLEAN, default false. Output the same BOOLEAN.

That's the whole mechanism: get_value returns whatever value is. No state, no caching, no math. If you need the inverse, this pack also ships Boolean Invert; wire T into it and you've got an On/Off pair.

Why you'd actually use it

• A/B switches. Flip between two image paths or two strengths by routing a T through a Boolean switch node - the toggle is right there on the graph, not buried in a dialog.
• Muting expensive branches. Feed its output into a bypass/switch and you can kill an upscale pass or a ControlNet branch without deleting nodes.
• Conditional math. Drive a Math/compare node with a boolean so "on" means one formula and "off" means another.

Honestly, if you're on rgthree or a similar utility pack, you may already have equivalents - but T is tiny, dependency-free, and doesn't make you hunt for it. It's the kind of node you forget exists until you're tuning a workflow at 2am and want a switch in arm's reach.

Install

Same as every node in this pack: ComfyUI Manager → search CRT-Nodes → install and restart, or git clone https://github.com/PGCRT/CRT-Nodes into ComfyUI/custom_nodes. Because the whole suite loads together, you're getting the full 106-node dependency footprint for one little toggle - worth knowing before you install the pack for this node alone. If you only want the toggle UI, a lighter pack would do; if you're already in the CRT ecosystem, it's free.

There's essentially nothing to troubleshoot here - a boolean pass-through either outputs what you set or you've connected it to something wrong. The one thing to remember: it's an output value, not a persistent latch. It doesn't remember state between runs the way some seed nodes do; whatever the widget shows is what it outputs.