toobusy Bundle Unpack

The toobusy pack's whole reference-production flow runs on a custom data type called TOOBUSY_BUNDLE - a single wire that carries images, audio, prompts, and LoRA selections from the Reference Board through the Prompt Director and into Flux2 Klein. That's great until you want to use the bundle outside the fold, or you need to inspect what's actually in it. toobusy Bundle Unpack is the escape hatch: one input, seventeen named outputs, and suddenly your opaque bundle is a wall of plain sockets you can wire anywhere.

How it works

There's no magic here - the bundle is a structured payload, and this node reads named slots out of it. The image side unpacks the role-based cards: character_a_image, character_b_image, face_a_image, outfit_a_image, pose_a_image, background_a_image, style_a_image, and prop_a_image. The audio side gives you audio_a / audio_b plus their durations as floats. Then the text side exposes the assembled resolved_prompt, the negative_prompt, and the selected LoRA as selected_lora_name + selected_lora_strength. There's a debug_json output with the raw payload for when you want to see what a node upstream actually put in there.

The socket names mirror the bundle's role vocabulary, so if you built a bundle on the Reference Board with Character A and a style card, character_a_image and style_a_image are where they land.

What you'd use it for

• Inspection. A debug_json output is the honest way to learn what your Reference Board and Director actually produced before you trust the fold.
• Wiring outside the fold. Feed character_a_image into a regular Load Image-style consumer, or route resolved_prompt into a plain CLIPTextEncode if you're not using Flux2 Klein.
• Feeding the DreamID talking-head nodes. The DreamID Talker takes a bundle directly, and Bundle Unpack is how you see what it's about to talk over.

The image outputs and audio outputs are the ones beginners actually use; the duration floats matter if you're syncing audio to video length downstream.

Install and gotchas

Standard pack install - ComfyUI Manager search "toobusy", or:

cd ComfyUI/custom_nodes
git clone https://github.com/nicekriss/toobusy.git toobusy

Restart ComfyUI. No optional dependencies; the bundle type is core to the pack.

Two notes. First, empty slots come through as blank outputs rather than errors, which is friendly but means you should check the socket's connected before assuming a bundle actually has a style card. Second, this node doesn't validate - if you unpack a bundle from a workflow where the upstream nodes are from a different toobusy version, the payload shape is the contract, and old bundles may not match new sockets. Re-run upstream after updating the pack. If all you need is one specific image out of the bundle, the sibling Bundle Get node is the lighter version - this one is for when you want everything.