Fatha Template

The Fatha Template is the derp-UI starting point for the pack's newer generation of nodes, and the display name tells you the framework: "Fatha Template," named after the Fatha rendering system the pack's modern nodes are built on. Where its sibling, the Uncle Template, keeps classic input/output sockets, the Fatha Template is a pure virtual shell - no sockets at all - which is exactly what a wireless-signal node looks like before you give it a job. Part of xcp_derp-UI (search "xcp_derp-UI" in ComfyUI Manager, by lordwedggie), under derpNodes/Templates.

What it is

Check the node class and it's about as minimal as a node gets: empty required inputs, empty return types, a do_nothing function, and the 🔞 derpNodes/Templates category. The real content is in the JavaScript - a virtual Fatha child that handles layout, theming, title persistence, and the wireless signal plumbing, so a developer starting a new derp node inherits all the framework machinery instead of rebuilding it.

The index describes it as a "virtual Fatha shell for building custom derp nodes," and that's the whole job. You pick this template when the node you're building will broadcast its output wirelessly (like the pack's sliders, toggles, and loaders, which all ship as pure virtual shells with no sockets) rather than move data over visible wires.

Why two templates?

It's genuinely a fork in the design road, and worth understanding even if you never build a node: derp-UI has two node frameworks. Uncle nodes keep real LiteGraph sockets - they play nice with default ComfyUI wiring, and Seed V2 and the Uncle Template live there, along with their documented layout quirks. Fatha nodes are the modern path: full custom layout, docking support, and wireless broadcast, at the cost of not exposing classic sockets (which is fine because they don't need them). The Fatha Template is the flag planted for "new nodes should be built here." The pack's own trajectory - Seed V3 being the Fatha rewrite of Seed V2 - is the author voting for Fatha with actual code.

Install

cd ComfyUI/custom_nodes
git clone https://github.com/lordwedggie/xcp_derp-UI-Release

Restart ComfyUI. No pip requirements, no model downloads, no npm step. Manager users: search xcp_derp-UI.

Honest takes

For end users, this node does nothing and is meant to. It's scaffolding for node developers, full stop. If that's not you, the most useful takeaway is the framework story it represents: this pack is betting its future on its own rendering stack - the KB's comfyui-ecosystem.md documents how fragile the ecosystem's custom-rendering situation is around the Nodes 2.0 frontend, and derp-UI's answer is to support both frontends and own its rendering layer entirely. That's ambitious for a small pack, and it's both the source of its personality and the source of its risk. If you're evaluating whether to depend on derp-UI for anything serious, this template - and the pack's architecture docs - are worth reading before you commit.