rgthree-comfy: ComfyUI Node Pack for Cleaner Workflows

What rgthree-comfy Adds to a ComfyUI Graph

ComfyUI workflows get messy in predictable ways: reroutes multiply, seeds are retyped by hand, several Loras need toggling between runs, and values like steps or cfg have to be re-entered on every sampler. rgthree-comfy is a set of custom nodes aimed at those annoyances. The README describes it plainly as "a collection of nodes and improvements created while messing around with ComfyUI," written by the author for his own workflows.

The target user is someone who already builds ComfyUI graphs and wants fewer clicks per run. The Context and Context Big nodes carry general flow properties forward and merge new data, which the README compares to other suites' "pipes" while claiming easier merging. The Seed node mirrors Automatic1111's seed control, including "-1" for a random seed each run and quick actions to randomize or reuse the last queued seed. Power Lora Loader stacks multiple Loras in one condensed node with per-row toggles. None of this changes what the sampler computes; it changes how much of the graph you maintain by hand.

How Context Nodes and the Seed Node Actually Behave

The mechanism is graph-level, not model-level. Context and Context Big are backwards compatible with each other: an input connected to a Context Big passes through CONTEXT outputs on normal Context nodes, and outputs that exist only on Context Big, such as steps, are available there. That means you can insert a Context node mid-graph without rewiring the whole chain. The README also notes a shortcut: dragging a Context output over another node and holding ctrl on release connects the remaining Context outputs to the hovered node.

The Seed node stores its value in image metadata, so dragging an image back into ComfyUI fixes the seed field to that image's seed. Two values not shown in the menu exist: "-2" increments the last seed and "-3" decrements it, falling back to a random seed if there is no previous value. Power Lora Loader has no stated limit on rows, and its right-click menu moves rows up or down for presentation only, without affecting the image. A Show Strengths property switches between one strength for both model and clip, or separate fields for each.

Installing rgthree-comfy and Running a First Context Chain

The README gives three steps: install ComfyUI, clone the repository into custom_nodes, then start ComfyUI. The clone target in the README is the folder named custom_modules, while the shell command changes into ComfyUI/custom_nodes; follow the path you actually have on disk.

cd ComfyUI/custom_nodes
git clone https://github.com/rgthree/rgthree-comfy.git

After restarting ComfyUI, the nodes appear in the node search. A first useful exercise is a Context chain: add a Context node, feed it your positive conditioning and seed, then connect its CONTEXT output to a second Context node further down. Values entered on the first node show up downstream without new wires.

Settings live behind a right-click on empty graph space, under rgthree-comfy > Settings (rgthree-comfy), or in the ComfyUI settings dialog. They are stored in rgthree_config.json inside the rgthree-comfy directory. The README states that advanced settings exist only in that file, and that you can copy rgthree_config.json.default to rgthree_config.json before modifying it.

cp rgthree_config.json.default rgthree_config.json

For a Lora stack, add a Power Lora Loader, click + Add Lora for each file, and toggle rows on or off. The README notes the deprecated Lora Loader Stack node should be replaced by Power Lora Loader.

Where rgthree-comfy Breaks or Is the Wrong Choice

The README is upfront that the nodes were made for the author's own use cases, and it offers no support commitment. That matters when a ComfyUI update changes frontend behaviour: the settings dialog exists partly because, in the README's words, "perhaps a future ComfyUI change breaks rgthree-comfy." You can disable individual features there, but you are the one diagnosing the break.

The release history is thin. The only listed release is v.1.0.0 from 2023-09-12, while pyproject.toml carries a version string of 1.0.2608312342 and the last push to the repository was on 2026-09-01. There is no changelog in the repository, so pinning to a tagged release is not a supported path here. If your team needs semantic versioning and release notes before upgrading a shared ComfyUI instance, this pack does not provide them.

Several nodes are also narrow. Image Inset Crop crops by pixel or percentage and does nothing else. Display Any shows backend text after execution, so it is useless for values you need during graph construction. The Bookmark node is a navigation aid, not a workflow primitive. If your graphs are already small and stable, the added node types may cost more in reading than they save in clicking.

rgthree-comfy Versus ComfyUI's Built-in Nodes

ComfyUI ships its own reroute and primitive nodes, and many users never leave them. The difference is in what each node carries. A stock reroute moves one link; the rgthree-comfy Reroute node, per the README, supports multiple directions and sizes, with width, height and connection layout changed from the right-click menu, plus toggles for resizability and title or type display. The minimum size when resizing is stated as 40x43.

Context nodes are the bigger divergence. Instead of separate primitive nodes feeding each sampler, one Context node bundles properties and passes them along, and Context Big exposes additional outputs like steps. That is a genuine architectural choice: fewer wires, but a graph whose values are less visible at a glance, since the Context node holds them rather than the sampler. For a two-sampler graph the built-in nodes are clearer. For a long chain with repeated settings, the Context approach removes a class of rewiring errors. The README does not document how Context interacts with third-party pipe-style nodes, so mixing both in one graph is untested territory.

Licence, Maintenance and Upgrade Cost

rgthree-comfy is MIT licensed, with the licence file at the repository root and pyproject.toml declaring license = { file = "LICENSE" }. MIT permits commercial use and modification; the practical obligation is keeping the copyright notice with any redistributed copy. That is a summary of the licence identifier, not legal advice for your situation.

The last push was on 2026-09-01, so the repository is not archived and has seen recent activity. There is no published release cadence to plan around, and no migration guide in the repository. Upgrading means pulling the repository and restarting ComfyUI, then rechecking your rgthree_config.json against rgthree_config.json.default for new keys. The build script is ./__build__.py, run through npm run build, and it targets the web assets rather than the Python nodes. If you install from a git clone, expect to resolve any breakage yourself.

Editorial conclusion

Adopt rgthree-comfy if you already run ComfyUI and want the Context nodes, Seed node, Power Lora Loader or Reroute improvements in your graph. Skip it if you need documented support channels or a versioned release cadence, since the README states the author built it for his own use cases. Before installing, confirm your ComfyUI instance and check the rgthree_config.json.default file so you know which settings you are turning on.

Frequently asked questions

Official sources

1. Issues
2. License: MIT
3. README
4. Releases
5. rgthree/rgthree-comfy on GitHub