H3 Studio • Workflow Note

H3 Studio is a big workflow. It runs a 33B diffusion model, juggles up to nine ordered references, keeps four different caches warm, and hides most of that behind a Director node. When you open someone's shared H3 Studio workflow, you want to know which profile they used and why, what's optional, and where the sharp edges are - before you hit Queue and watch a slow, expensive run. H3StudioWorkflowNote (H3 Studio • Workflow Note) is the pack's answer: an actual documentation card living inside the graph, so the instructions travel with the workflow instead of living in a GitHub readme nobody reopens.

What it actually is

A Markdown note node. That's the whole job, and it's deliberately boring. It has a section label that slots your note into a visual category, a text field that holds Markdown, and - the important part - zero outputs. It doesn't participate in generation, it doesn't affect your seed or cache, and it has no effect on the pipeline whatsoever. You can edit it, delete it, or leave it hanging disconnected and nothing changes except the documentation.

How it works

The text is rendered safely in the frontend with Preview/Edit modes - preview to read, edit to change. The section enum gives you five buckets to keep a workflow organized: quick start, models, settings, optional / experimental, and troubleshooting. That's a small thing that does a lot for a workflow this dense: a quick-start note at the top, a settings note next to the Director, and a troubleshooting note at the bottom is a self-documenting project. One guarantee worth knowing from the tooltip: the text is rendered safely and never sent to MiniMax H3 - it's purely local documentation, not another input sneaking into your prompt.

The inputs that matter

Both are trivial:

• section - the label bucket, default quick start. Pick the one that matches what the note is for.
• text - your Markdown. Multiline, and it's the entire content of the card.

Install

It's part of the H3 Studio pack - ComfyUI Manager (search ComfyUI-MiniMax-H3-Studio) or:

cd /path/to/ComfyUI/custom_nodes
git clone https://github.com/thaakeno/ComfyUI-MiniMax-H3-Studio.git
cd ComfyUI-MiniMax-H3-Studio
python -m pip install -r requirements.txt

Restart and hard-refresh. No models needed - this node's entire dependency is the frontend.

Where people get burned

Honestly, there's not much to burn. The one thing to internalize: because it's a no-output node, ComfyUI won't run it as part of your generation graph, so a note can't be a hidden gotcha that silently changes results. The only genuine footgun is the opposite - expecting it to do something. It's documentation. If you're building workflows to share (and H3 Studio workflows are very shareable, with the save node carrying full project state), put a note at the top saying what models and profiles the workflow assumes, and a note by the sampler saying what to change first. Future-you, and anyone you share with, will thank you. The pack itself is alpha and classic-frontend-only, but this particular node is the most stable thing in it.