凤希AI - 整数输入

FxAiInputInt is the integer twin of the pack's float-input node: you type a whole number into 输入数字, and it comes back out as 输出, untouched. No math, no conversion, nothing clever. It exists for one reason - so a number that several nodes need (a frame count, an index, a seed, a repetition count) has a single home in the graph instead of being retyped in five places, guaranteeing all five stay in sync.

Every serious ComfyUI graph is mostly plumbing, and value nodes like this are the load-bearing part of it. The pattern is older than this pack: it's the same "one authoritative source, fan out to many consumers" idea behind core ComfyUI's primitive nodes, and this node is simply that idea as a dedicated, typed widget.

How it works

The implementation is return (输入数字,). Input passes straight through. You set the value on the node's widget once, then wire the 输出 into every INT input that needs the same number - sampler steps, batch sizes, frame indices, whatever. Change it at the source and every consumer updates together. In loop-style workflows - which this whole pack is built around - that's the difference between a config you can tweak and a config you have to excavate.

Inputs and outputs

• 输入数字 (INT, default 1) - the value.
• 输出 (INT) - the same value.

That's the whole contract. If a downstream input needs a float instead, don't fight the type system - the pack's FxAiIntToFloat node bridges that in one hop.

Installing it

Part of fxai-toolkit (凤希AI, MIT). Install via ComfyUI Manager (search "fxai-toolkit") or:

cd ComfyUI/custom_nodes
git clone https://github.com/fxai666/fxai-toolkit
# restart ComfyUI

No models, no dependencies beyond the pack's first-load auto-install of soundfile and psutil. Chinese labels; support via the author's QQ group (775649071) and Bilibili.

Where people get burned

The usual failure isn't the node - it's forgetting it exists and typing the same integer into a dozen widgets, then chasing a mismatch when one of them was updated and the others weren't. The one genuine quirk: it's strictly an int source, so if you wire it into a FLOAT socket you'll get a type error; keep the conversion nodes handy. And as with all primitive nodes, remember the value lives on the widget - save the workflow, and the number travels with it, which is usually what you want but means it isn't dynamic.