rgthree

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