MiniMax H3 Creator × Long Video Background Start / 创作工作区后台绑定 (Advanced/T8)

Long Video background jobs are the workhorse of marathon H3 shoots - a queue that renders candidates in the background while you keep tweaking. The Creator Workspace is the "plan shots and variants" layer. MiniMaxH3CreatorBackgroundStartT8Advanced is the bridge between them: it binds one Creator Workspace hash to the existing, proven Long Video background queue/cancel/retry controller so your planned shots actually get rendered by the machinery that already works.

The key design constraint, stated plainly in the description: this node binds, it doesn't own. It hands your workspace's hash to the Long Video background controller and gets back a job_id and the controller's background_state_json. It doesn't reimplement the queue, it doesn't silently start rendering, and in its default review_only mode it doesn't mutate anything at all.

The inputs

• workspace (custom H3_T8_CREATOR_WORKSPACE) - the plan you've already reviewed. The node hashes it and binds that exact hash; a different workspace means a different job.
• chain_id (creator_long_video) - which background chain the workspace binds to.
• execution_mode - review_only (default) is non-mutating; flip to a real execution mode only when you're ready to render.
• max_retries (1) and retry_delay_seconds (2) - the retry envelope for the background job.
• release_policy (clear_execution_cache) - what happens to the execution cache when the job releases.

The outputs

workspace (the bound one, passed back so downstream nodes see the binding), chain_id, auto_accept (whether the bound chain will auto-accept completed candidates), job_id, and background_state_json - the last one is the live feed you'll hand to the Run Select node so it can pick the next shot based on what actually finished.

The usage constraint that matters

The README is blunt: use it only with the Long Video candidate-save / Auto-Accept terminal chain. If you wire it into a chain that doesn't save candidates, you get a binding with nothing to act on, and the pack treats "review-only or unbound" as a state that blocks downstream generation rather than one that silently proceeds. A real test the README documents: a 256×256×22 sample that was cancelled after a quarter of the steps, with VRAM returning to baseline +90MiB after the directed cancel - the point being this bridge respects the background controller's own lifecycle instead of fighting it.

Install

Standard pack install:

cd ComfyUI/custom_nodes
git clone https://github.com/T8mars/comfyui-minimax-h3-audio-T8

Restart ComfyUI. No extra dependencies beyond what the Long Video chain already needs (ffmpeg on PATH for candidate saving). It's in T8/MiniMax H3/Studio/Experimental, and the reference workflow is 2026-08-23_H3_Creator_Long_Video_Background_Bridge_Advanced_EXP.json in 11-studio-production. Start in review_only with a tiny canvas, confirm the binding hash and job_id look sane, then graduate to real execution.