Input Integer (ShellAgent Plugin)

Input Integer (ShellAgent Plugin) is the whole-number entry point in the ShellAgent input family: a named INT slot that a calling app fills in at runtime - steps, batch size, frame counts, seeds - with a widget you can set by hand while you're testing.

It's the most configurable of the pack's number inputs, and the extra fields are the reason you'd pick it over the float version: minimum, maximum, and step. Together those three give the app everything it needs to render a proper stepper or slider with sensible increments instead of a raw number field.

How it works

The validate() method reports the input's schema to ShellAgent - title from input_name, type integer, with your min/max/step baked in. The app builds its form, injects the chosen value, and the node hands it out on the int socket. Standalone, the widget's default_value is just what comes out. step defaults to 1 and is clamped to 1–10000, which covers most generation knobs.

Inputs that matter

• input_name - the variable name the app sees. Default input_integer.
• default_value - used when the app doesn't supply a value. Also what you type in while testing.
• minimum / maximum - set both. Like the float node, the defaults are 0 and 0, and a 0-to-0 range renders as a locked slider in the app.
• step - the increment. Default 1.
• description - optional help text for the app's UI.
• choices - optional discrete picklist ("manage choices" button, same as Input Text) if you want fixed options instead of a stepper.

Output: a single INT on the int socket.

Installing it

Same one-pack install:

cd ComfyUI/custom_nodes
git clone https://github.com/myshell-ai/ComfyUI-ShellAgent-Plugin

restart, or grab ComfyUI-ShellAgent-Plugin from ComfyUI Manager. No model downloads; the pack's pip requirements install with it.

Common issues

• The app's stepper is stuck at 0. minimum/maximum left at defaults - set real bounds.
• Values jump by 1 when I wanted 10. Change step.
• The app shows a free number box. Give it bounds; a range is what unlocks the stepper UI.
• Seed gets reused between runs. If you wired this to a seed input, the app sends the same value every run unless you vary it on the app side - that's a caller problem, not a node problem.

Tiny node, tiny job, and the min/max/step trio is genuinely all there is to it. Set the bounds, name it well, and move on.