VibeTransferOption ✒️🅝🅐🅘

NovelAI's vibe transfer is the "I can't describe this style, so here's a picture of it" button, and VibeTransferOptionNAID is how you hit it from ComfyUI. Give it a reference image, wire its NAID_OPTION output into the option input on GenerateNAID, and your next generation inherits the reference's style and feel - lighting, palette, texture - while the prompt still decides the actual content. It's the option node you'll reach for when a LoRA would be overkill and a prose description keeps failing.

The inputs:

• image - the reference. It gets resized to the generation size, so composition in the reference matters more than resolution.
• information_extracted - 1.0 default. How much of the reference's content the API actually reads. This is the "how hard do we squint at it" knob; crank it down and the transfer gets looser.
• strength - 0.6 default. How hard the transferred vibe is applied. Lower it for a subtle nod to the reference, raise it toward 1.0 for "make it look like this."

The interesting part is that this node has an option input itself, and it appends to a list rather than overwriting. Connect two VibeTransferOptionNAID nodes into each other (or into a shared chain) and the pack sends both references as a reference_image_multiple array - the README shows exactly this as its "Multiple Vibe Transfer" workflow, and it's the way to blend two styles into one image. You can also chain a ModelOptionNAID or NetworkOptionNAID onto the same branch, since Generate merges all the option dicts it receives.

Mechanically it's the same honest API-client story as the rest of the pack: the node stores (image, information_extracted, strength) in the option dict, Generate base64-encodes each reference and packs it into reference_image_multiple, reference_information_extracted_multiple, and reference_strength_multiple for NovelAI's servers to chew on. All paid in Anlas, all done off-machine.

Two practical notes. First, vibe transfer combines fine with img2img - feed a source through Img2ImgOptionNAID and a style reference through a vibe node and you get "same composition, different vibe," which is the combo the README's own screenshots demo. Second, the reference really is just for style: unlike the character-reference node, there's no identity retention here, so don't expect the person in the reference to show up in your output. For that you'd want the CharacterReferenceOptionNAID node in the same pack.

Install is the pack standard - Manager search "ComfyUI_NAIDGenerator", or clone into custom_nodes/ and restart - with the usual .env requirement for NAI_ACCESS_TOKEN in the ComfyUI root. If the node is silently returning nothing, that's the first thing to check, alongside the console for swallowed API errors.