Task Selector

Task Selector is the pack's helper for the single most consequential choice in a Wan 2.2 workflow: are you generating from text or animating a reference image? One dropdown, one output, and the value it produces is type-compatible with Sampling Plan (Wan 2.2)'s task input. It exists so the T2V/I2V decision lives somewhere you can actually see and switch it.

Why the choice matters this much

Wan 2.2 uses different expert boundaries per task, straight from the official configs: 0.875 for T2V, 0.900 for I2V. That boundary is the sigma where the workflow hands off from the high-noise expert to the low-noise expert. Get the task wrong and you're handing off at the wrong sigma - the plan's split lands off the boundary, and you get the kind of muddy, inconsistent video that sends people into "is my Wan install broken?" debugging sessions. So this one dropdown is quietly controlling where every Wan 2.2 workflow changes experts. It also matters that I2V anchors the first frame to a reference image - the community's preferred workflow for consistency - while T2V starts from pure text, and the two genuinely want different sampling.

What it does

Takes a task input with two options - T2V and I2V (default T2V) - and outputs it as a typed combo value for the plan. The output type is a custom enum, so ComfyUI only lets it plug into inputs that expect a task value; the wiring mistake gets caught by the type system before you hit Queue.

The reason to use the helper instead of the plan's own dropdown is the same as the pack's other selectors: when one mode switch also controls latent inputs, image encoders, and other task-dependent branches, you want a single visible control feeding all of them rather than remembering to flip several widgets in sync. Group it with the rest of the task-dependent nodes and muting the group takes the whole branch with it.

Install

Under sampling / Sampling Planner / Helpers, standard pack install:

cd ComfyUI/custom_nodes
git clone https://github.com/boobkake22/ComfyUI-SamplingPlanner

or ComfyUI Manager (search Sampling Planner), then restart. No models, no dependencies.

The honest take: it's a one-option nicety, not a workhorse - the plan's own task dropdown works fine if you're building a single-purpose workflow. It earns its place the moment you have a graph that does both T2V and I2V through one planner, because that's exactly when a hard-to-see task setting becomes the source of an expensive wrong-render bug. Two options, one output, and it's the cheapest insurance against handing off at the wrong boundary.