Concurrent Submit | Zhenzhen WanX 2.6 Video

If you've been around local video generation, you know Wan - 2.1 and 2.2 are open weights, and 2.2 is still the community's quality default. What you may not have registered is that Alibaba stopped shipping weights after 2.2: Wan 2.5, 2.6, and 2.7 are all API-only. There is no local Wan X 2.6. This node is the cloud door - it's the pack's Wan X 2.6 video node (Comfly_wan2_6_API, category zhenzhen/wanx), rebuilt as a concurrent Submit. Same Wan 2.6 generation, but it drops the job into the shared video pool (ten workers) and hands you a task to collect in Concurrent Collect Videos.

The pack's changelog is honest about this one's origin: it was built for the official Alibaba Bailian (百炼) API key, tested by the author before the model landed on the Zhenzhen site proper. In the shipped code it reads the same api_key field as the rest of the pack, so the practical setup is just like every other node here.

Inputs that matter

• prompt - comes with a long Chinese example prompt (a graffiti character rapping under a railway bridge - the kind of demo that shows off Wan's audio + motion together). Replace it; it's a starting point, not a recommendation.
• image - optional reference for image-to-video. Connected images get base64-encoded and sent as img_url.
• resolution - 1080P (default) or 720P.
• duration - 5, 10, or 15 seconds.
• prompt_extend - on by default; Wan's server-side prompt rewriting.
• shot_type - single or multi (default). Multi-shot is Wan 2.6's storyboard-ish mode where one prompt yields multiple shots in one video.
• audio_enabled - on by default. Wan 2.6 generates audio; audio_url lets you supply your own track instead.
• api_key, skip_error, seed - standard. seed is the pack's cache-control seed (see below).

Output: a COMFLY_VIDEO_FUTURE task.

How it works

Standard concurrent machinery: ComflyConcurrent.py validates, pushes the real Comfly_wan2_6_API call onto the bounded video executor (ten workers), and returns the future immediately. The original node posts to the Wan API, polls the task, and wraps the result in a ComfyVideoAdapter; the wrapper just moves the wait to the collector, which restores slot order and reports per-slot status. failure_mode: placeholder degrades failures to blank clips.

Setup

Install the pack once - ComfyUI Manager (search "Comfyui-zhenzhen"), or:

cd ComfyUI/custom_nodes
git clone https://github.com/T8mars/Comfyui-zhenzhen

No weights to download - Wan 2.6 has none to give. You need a key from ai.t8star.org (overseas) or api.seedance.nz (domestic), and every clip is a metered call.

Gotchas

The seed field here is a compatibility seed - the tooltip is explicit that it controls ComfyUI's cache (fixed reuses the cached result, randomize requests a new run) and is not sent to APIs that have no native seed. Don't expect it to give you Wan 2.6's reproducible output. Prompts are capped at 1500 characters; the default demo is near that, so write tight. And the local-vs-cloud reflex matters more here than anywhere: this is the model the community watched go closed, and no local checkpoint exists to fall back to - if you need open Wan, you want 2.2, not this node. Timeouts: check the async task page before assuming the job died.