ComfyUI Node

Note _O

Your workflow's margin notes, minus the margin

By omar92·Created 3 years ago·Updated 5 months ago· 181
Note _O
      text

      If you've ever dragged a workflow PNG back onto a ComfyUI canvas and stared at 40 nodes wondering what any of them were for, you already know why Note _O exists. It's a sticky note: one big multiline text field, zero outputs, and absolutely nothing else. You put it next to a section of the graph, type "this is the hires-fix pass, don't lower denoise below 0.4," and when you share the workflow - or come back to it six weeks later - the explanation is right there in the graph.

      It's in the Quality of Life Suit pack under O/utils, marked as an output node because it produces nothing and exists purely for the canvas. The beauty of it is how well it fits ComfyUI's sharing culture: a workflow is a JSON file that travels inside the output PNG, and a note travels with it. Your text is embedded in the workflow, so a note is documentation that can't get separated from the thing it documents.

      How it works

      Note _O has a single required input, text, with multiline enabled, and its function returns nothing (()). That's the whole mechanism - there is no execution, no pass-through, no side effects. It's a comment node that happens to look like a widget.

      The one practical thing to know: because it's a plain node, you can't format the text beyond what a text box allows. You're not getting rich text or colors - just honest ASCII explanations. If you want to color-code sections, you're better off giving nodes meaningful names in the canvas settings.

      Installing

      Pack-wide, same as every node here:

      cd ComfyUI/custom_nodes
      git clone https://github.com/omar92/ComfyUI-QualityOfLifeSuit_Omar92.git
      

      or search ComfyUI-QualityOfLifeSuit_Omar92 in ComfyUI Manager, then restart ComfyUI (not just refresh the browser). No dependencies, no models, no config - it's the cheapest node in the pack to run.

      Any traps?

      The only trap is expecting more from it than it is. It won't show you values at runtime, it won't log to console, and it won't help you debug - for that, this same pack has Debug Text _O under O/debug, which prints to the terminal. Note _O is purely for humans, and it's honestly the most underrated node in the suite. Every messy workflow you've ever downloaded would have been 50% easier to understand if the author had scattered a few of these around.

      CategoryO/utils

      Inputs (1)

      NameTypeDefaultDescription
      textSTRING

      Outputs (0)

      No outputs