Nodes/comfy-ninfer-api/NInfer - Server Control
ComfyUI Node

NInfer - Server Control

Drives the NInfer process directly. The `trigger` input sets when this node runs; `done` marks when it has finished. Status is shown here as preview text, not as a connectable port.

By kaerozhi·Created 2 days ago·Updated 2 days ago· 1
NInfer - Server Control
  • trigger
  • Done
◄actionensure running►
◄model_fileHuihui-Qwen3.8-27B-abliterated-Swift-1.5-GSQ-RCO-IQ3_S-mtp.ninfer►
◄forcefalse►
◄languagezh►
CategoryNInfer

Inputs (5)

NameTypeDefaultDescription
actionCOMBOensure running4 options: ensure running, stop, keep alive, status
model_fileCOMBOHuihui-Qwen3.8-27B-abliterated-Swift-1.5-GSQ-RCO-IQ3_S-mtp.ninfer1 options: Huihui-Qwen3.8-27B-abliterated-Swift-1.5-GSQ-RCO-IQ3_S-mtp.ninfer
forceBOOLEANfalseSkip the graceful shutdown and kill the process outright
languageCOMBOzhLanguage for the status text this node prints. ComfyUI's own node labels follow the interface language.
triggeropt*Anything can feed this. Its only job is ordering: this node runs after the wired input finishes. Wire a chat reply here to `stop` as soon as the reply is produced.

Outputs (1)

NameTypeDescription
DoneNINFER_CONTROLSequencing signal only. Downstream nodes wait for it. It is a dedicated control socket and cannot feed data inputs like a model id.