IDEO_INFO

ComfyUI node packs have a habit of "improving" a node by collapsing twenty sockets into one bundle, and then every existing workflow that used the old sockets breaks. IAMCCS IdeoInfo is the bridge for exactly that migration. When the newer StoryboardFrame V2 started shipping a single IDEO_LINX output, this node takes that one bundle and fans it back out into all the technical outputs the older FrameDesigner V2 used to expose. Old workflow keeps working, new backend keeps its clean interface. Everybody wins.

It's a pure passthrough adapter. The one required input, IDEO_LINX, has the author's own tooltip spelling it out: "Connect the single IDEO_LINX output from IAMCCS StoryboardFrame V2. This node exposes the same technical outputs the FrameDesigner V2 previously had."

What you get out

Twenty outputs, and most of them only matter if you're deep in the Ideogram frame pipeline:

• positive - the CONDITIONING for the sampler. This is the one that actually reaches the KSampler.
• prompt_json, width, height - the frame's prompt and canvas.
• i2i_canvas_image, i2i_enabled, i2i_denoise, low_sigma_start_step, i2i_report, reference_noise_mask, reference_mode - everything the image-to-image continuation path needs (denoise strength, which steps to re-noise from, the reference mask).
• target_x/target_y/target_width/target_height and target_panel_width/target_panel_height - crop geometry for paneling.
• bboxes, paint_mask, gemma_json_request, debug_report - the rest of the technical surface.

It also appends a small info report to debug_report (tensor types, prompt hash/char count, bbox count) every time it unpacks - cheap observability while you're wiring things up.

Install & gotchas

Standard IAMCCS-nodes install - ComfyUI Manager (search IAMCCS) or:

cd ComfyUI/custom_nodes
git clone https://github.com/IAMCCS/IAMCCS-nodes.git

Then restart. No dependencies beyond the pack itself.

The one real failure mode is right in the code: if you feed it something that isn't a proper IDEO_LINX bundle, it throws a clear error about missing fields rather than silently returning garbage. So if you're seeing an error like "IDEO_INFO missing IDEO_LINX field(s)", the wire isn't carrying what you think - check that the source really is the FrameDesigner V2 output, not an older design-bundle output with a similar name.

Do you need it?

If your workflow was built around FrameDesigner V2's separate sockets, yes - this is the compatibility shim that keeps it alive. If you're starting fresh, you can usually wire the FrameDesigner output directly and skip the extra hop; the bundle only needs unpacking when you're touching the individual technical signals, especially the i2i or bbox outputs.