rgthree

1# rgthree-comfy
2 
3`rgthree-comfy` is one of the most widely installed packs, so its nodes turn up in a
4large share of community workflows. Three of its properties make it a recurring
5agent-failure mode — all three fail *quietly enough* to look like success.
6 
7## The three things that catch agents out
8 
9**1. Some rgthree nodes are FRONTEND-ONLY.** They are registered by the pack's JS
10(`registerCustomNodes()`), have no Python class, and are therefore **absent from
11`/object_info` by design**. Checking `/object_info` and concluding "this node doesn't
12exist" is wrong. `/object_info` lists 24 rgthree *backend* types; the toggles are not
13among them.
14 
15**2. They are configured through PROPERTIES, not widgets.** `matchTitle`,
16`toggleRestriction` and `sort` live in `node.properties` (right-click → Properties),
17not in `widgets`. Use **`panel_set_property`**. `panel_set_widget` does not silently
18half-work — it **refuses**, with `has no widget "matchTitle" (available: …)` listing
19the widgets that do exist. That refusal is the fastest confirmation you are on the
20properties path; read it rather than retrying the write.
21 
22**3. Fast Groups nodes take NO wiring and enumerate GROUPS by title.** Leave the
23`OPT_CONNECTION` output unconnected. The node renders one toggle per matching group,
24so **the groups must exist and be named before the node is useful**.
25 
26## Which rgthree nodes `panel_add_node` will actually add
27 
28The panel authorizes every add against fresh `/object_info` and **fails closed** on a
29…