SharkOptions Guider Input

This is an adapter. SharkOptions Guider Input takes a ComfyUI GUIDER - the object produced by nodes like CFGGuider or one of the custom guidance nodes - and packs it into the OPTIONS bundle that RES4LYF's Shark/Clown samplers consume. It's the bridge between ComfyUI's standard "custom sampling" guidance world and RES4LYF's own options-chain world.

You reach for it when the guidance you want lives outside RES4LYF. ComfyUI's advanced sampling nodes let you build a guider with a specific CFG behavior, or a specialized guidance module, and normally you'd wire that straight into SamplerCustomAdvanced. If you'd rather run RES4LYF's solvers instead, this node lets you carry that same guider into them. Small node, narrow job, but it's the thing that stops you having to choose between the two ecosystems.

How it works

RES4LYF samplers don't take a GUIDER directly - they take an OPTIONS bundle you assemble by chaining configurator nodes. This node wraps your guider into that bundle and, if you chain in an existing OPTIONS, adds it alongside whatever's already there rather than clobbering it.

The inputs and outputs that matter

• guider (GUIDER) - the guidance object from whatever guider node you built. This is the required input and the whole reason the node exists.
• options (optional OPTIONS) - chain another options node in here to combine settings; leave it empty to start a fresh bundle.

Output is options (OPTIONS) - route it into the RES4LYF sampler's options input, or into the next link of your options chain.

How to install it

Part of the RES4LYF pack. ComfyUI Manager: search RES4LYF, install, restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/ClownsharkBatwing/RES4LYF/
cd RES4LYF
pip install -r requirements.txt

Portable builds use the embedded pip. Restart, hard-refresh (F5). rgthree-comfy is worth adding so the options and sampler menus nest cleanly.

Common issues

The confusion here is almost always "which knob wins." If you set a guider with its own CFG and also set CFG on the sampler, you now have two places specifying guidance - decide which one owns it and neutralize the other so they don't fight. Second, an options bundle only does anything if it reaches the sampler: dangling this node's output, or letting a later options node overwrite it, is the usual reason a custom guider seems ignored. And this is niche by design - most RES4LYF workflows never need it, because the samplers already accept conditioning and CFG directly. Only pull it in when you specifically want an external guider driving RES4LYF's solvers.