Nodes/VELVET VICE — MiniMax H3/VELVET VICE MiniMax H3 — Profile Manager
ComfyUI Node

VELVET VICE MiniMax H3 — Profile Manager

Save your whole H3 setup as a named profile that survives restarts

By Velvet-Vice·Created 10 days ago·Updated 7 days ago· 2
VELVET VICE MiniMax H3 — Profile Manager
    • profile_name
    active_profile
    profile_scopeFULL H3
    profile_payload{}

    The H3 System Hub and Director expose a lot of settings, and the ones that matter - backend choice, turbo configuration, prompt-director mode, and so on - are exactly the ones you don't want to re-enter by hand every time you reload a workflow or switch between "I'm testing fast" and "I'm rendering the real thing." VelvetViceMiniMaxH3ProfileManager is the node that makes those setups persistent: named profiles you can save, load, rename, duplicate, delete, import and export.

    The critical implementation detail is in the description: "Profiles are stored under ComfyUI user data, outside this node pack." That's a deliberate architectural choice - profiles survive pack updates and re-installs because they live in ComfyUI's own user directory rather than inside the custom_nodes folder where an update would wipe them. If you've ever lost a workflow because a node pack update replaced its config files, you understand exactly why that separation matters.

    How it works

    Three inputs describe the profile transaction:

    • active_profile (STRING) - the name of the profile currently in play.
    • profile_scope - FULL H3 or LORA ONLY. The pack has both the whole H3 setup and LoRA configurations as first-class persisted objects, so a "LoRA-only" profile can be swapped without touching your model backend choices.
    • profile_payload (STRING) - the JSON state being saved or loaded for that profile.

    The node's output is profile_name (STRING), confirming which profile is active. The actual save/load/rename/import/export actions are driven from the node's frontend panel - the node class itself is the persistence backend plus the active-name handshake, and the JavaScript UI (this pack ships heavy frontend code, including a dedicated prompt_director_persistence module) turns those three inputs into buttons you can actually press.

    What you'd use it for

    The two-profile workflow is the obvious one: a TURBO TEST profile with the fast backend, GGUF weights, turbo steps and low quality preset for iterating, and a FINAL QUALITY profile with native weights, refine on, and the quality preset for the real render. The "persistent mode across workflow switches" feature the README highlights means your choice doesn't silently reset to defaults when you change graphs - which is precisely the kind of silent reset that has wasted people's renders before.

    Install

    Part of the pack:

    cd ComfyUI/custom_nodes
    git clone https://github.com/Velvet-Vice/velvet-vice-minimax-h3
    

    or ComfyUI Manager → velvet-vice-minimax-h3, then restart.

    One expectation-setting note: profiles store settings, not models. A profile can remember that you use the GGUF backend at Q8 and turbo steps of 8, but it can't conjure the model files if they're not on disk - the preflight monitor is where missing-file reality gets checked. And if profiles seem to vanish, look under ComfyUI's user data directory (not the pack folder) before assuming data loss; that's where they're written, by design.

    CategoryVELVET VICE/MiniMax H3

    Inputs (3)

    NameTypeDefaultDescription
    active_profileSTRING
    profile_scopeCOMBOFULL H32 options: FULL H3, LORA ONLY
    profile_payloadSTRING{}

    Outputs (1)

    NameTypeDescription
    profile_nameSTRING