Nodes/ComfyUI_JR_MiniMaxH3Node/JR MiniMax H3 Prompt Review & Continue
ComfyUI Node

JR MiniMax H3 Prompt Review & Continue

A human-in-the-loop gate for H3 prompts, right inside the graph

By Goldlionren·Created 21 days ago·Updated about 9 hours ago· 28
JR MiniMax H3 Prompt Review & Continue
  • pip
  • reviewed_prompt
  • pip
timeout_seconds3600
prompt

Some workflows deserve a "wait, let me read that before we spend an hour rendering it" step, and that's exactly what the JR H3 Prompt Review & Continue node is: a pause point where execution halts, the current prompt shows up in a review UI in your browser, and nothing continues until you've approved or edited it. The natural spot is right after the prompt optimizer, before conditioning and sampling burn GPU time on a prompt you haven't actually looked at.

It's a simple node with a deceptively important job, and it works in two modes. In STRING mode you feed a prompt into the optional prompt input and get back reviewed_prompt after you approve. In Director PIPE mode you connect a JR_H3_DIRECTOR_PIPE, and the node picks the review text as optimized_prompt > compiled_director_prompt (whichever the pipeline says is authoritative), then writes your approved text into a new pipe output. The review UI lets you edit the text before hitting Next/Continue, so it's not a yes/no gate - it's a final editing pass.

The one setting that actually matters

timeout_seconds, default 3600 (range 60–86400). This node blocks execution until the browser approves, and the default gives you an hour to wander off and come back. Set it lower if you're the type who queues a workflow and forgets about it.

The catch the README is blunt about: this node requires an active browser - the one that queued the job. If you close the tab, stop the queue, or the browser reconnects with a different client ID, downstream never runs. It is deliberately not suitable for unattended API queues. Stop, timeout, or a browser that closes without reconnecting all block downstream. On the plus side, a browser refresh mid-wait restores the pending review (it tracks by ComfyUI client ID), and the prompt only lives in limited in-memory state - nothing gets written to ordinary logs.

Install

One install for the whole pack:

cd ComfyUI/custom_nodes
git clone https://github.com/Goldlionren/ComfyUI_JR_MiniMaxH3Node
<your-comfyui-python> -m pip install -r ComfyUI_JR_MiniMaxH3Node/requirements.txt

or search ComfyUI_JR_MiniMaxH3Node in ComfyUI Manager. Use the same Python that runs ComfyUI, restart, hard-refresh the browser. The review UI is front-end JavaScript, so a stale cache after an update is the classic "I don't see the approve button" failure.

Troubleshooting

  • The workflow just sits there. That's the node working as designed - it's paused waiting for your browser. Check the node's UI for the prompt and the approve button. Don't requeue; that stacks a second wait.
  • Approve does nothing after an update. Hard-refresh the browser. The README explicitly warns that the preview/review JavaScript needs a fresh load after updates.
  • "It works in my headless API queue" - no it doesn't. If you need an unattended pass, skip this node (or use fail_mode-style handling upstream). The human gate is the feature.
  • String vs pipe conflicts. When a pipe is connected, the STRING input is ignored and the review text must match the pipe's authoritative text exactly - the node rejects a mismatch rather than silently using one.
CategoryJR MiniMax H3/Prompt

Inputs (3)

NameTypeDefaultDescription
timeout_secondsINT360060–86400
promptoptSTRING
pipoptJR_H3_DIRECTOR_PIPE

Outputs (2)

NameTypeDescription
reviewed_promptSTRING
pipJR_H3_DIRECTOR_PIPE