🔥Fire Banner

Ever collapsed a messy region into a subgraph and instantly lost all sight of what's happening inside it? That's the trade you make: tidy canvas, blind debugging. RectumFireBanner is the pack's answer to that, and the author calls it the pack's killer feature. Wire an image that lives inside a subgraph into it, and the preview shows up right on the node's face - out here, on the main canvas, where you can actually watch it.

ComfyUI's subgraphs are still bad at one thing: getting visual information out. A collapsed node hides whatever is rendering inside it, which makes modular workflows miserable to monitor. This node is a preview port in the wall. Drop one inside the subgraph, connect the image you care about, and the result appears on the graph without uncollapsing anything.

How it works

The backend is refreshingly honest about being a bridge. When it runs, it takes the incoming image, saves it to ComfyUI's temp directory as rf_banner_<uuid>.png, and sends a UI message. The frontend JS then patches the node to render that PNG inside its widget, with a cache-buster on the URL so it always fetches the newest frame. Mechanically it's a Preview Image that lives on the graph instead of in the output panel.

It has exactly two inputs, both required:

• image - the IMAGE whose preview you want to surface. Wire anything visual here.
• rf_banner - a string label for the banner. Think of it as the anchor text so you can tell banners apart at a glance.

That's it. No outputs - it's an output node, so it terminates whatever branch it sits on.

Where you'd actually use it

Modular and nested workflows, mostly. If you build a graph out of reusable subgraph building blocks, a banner in each one turns a wall of collapsed boxes into a dashboard you can scan while a queue runs. It's also handy for debugging a subgraph that's producing something wrong: banner the intermediate image, run, and look at the canvas instead of hunting through the output panel.

The honest caveat

This node lives in the RectumFire/Test category, which tells you a lot about its status. The README is upfront: the newer ComfyUI frontend and subgraph changes have made it "unstable and sometimes unpredictable," and that's an upstream frontend problem, not a finished redesign. If you've been through the Nodes 2.0 churn - the Vue rewrite that broke rendering for packs like rgthree - you know the drill. On the classic canvas it's fine; on the new frontend, expect odd behavior until upstream settles and the author adjusts.

Install

It ships in the RectumFire pack, which has no pip dependencies, no model downloads, no API keys - pure Python plus browser JS, Apache-2.0 licensed. ComfyUI Manager (search "ComfyUI-RectumFire") or:

cd ComfyUI/custom_nodes
git clone https://github.com/vladgohn/ComfyUI-RectumFire.git

Then restart ComfyUI. Because the banner is drawn by browser JS, do a hard refresh (Ctrl+Shift+R) after installing or updating, or the frontend won't have the code yet.

Troubleshooting

• No preview showing: make sure an image is actually connected, that the branch executed, and that ComfyUI's temp output folder is writable (that's where the banner writes the PNG).
• Preview behaves erratically: you're probably on the newer frontend, where the author has flagged instability. It's a known upstream problem, not a misconfig on your end.

For a small utility pack with essentially no community footprint yet, the banner is the one node that punches above its weight - when the frontend cooperates.