Seed and Int (WLSH)

Small annoyance, small node. ComfyUI's built-in seed widget carries a special SEED socket type, paired with the familiar fixed/increment/decrement/randomize control that shows up under any native seed field. Plenty of third-party nodes want that. Plenty of others just want a plain INT. When you're wiring one seed value to feed both kinds - say, a KSampler that wants SEED and a save-metadata node from some other pack that only accepts INT - you either duplicate your seed entry across two widgets and hope you never let them drift apart, or you reach for something like this node, which types the number once and hands it out both ways.

How it works. You set a seed value (0 up to roughly 1.8×10¹⁹, matching ComfyUI's own seed range) and get back two outputs: INT and SEED, both carrying the same number, just typed differently for whatever's on the other end of the wire. That's the entire node - no randomization logic, no generation-time increment behavior baked in beyond what the input widget itself offers.

Inputs: seed, a single required integer field. Outputs: INT and SEED, same value, two types. Wire SEED to anything expecting ComfyUI's native seed socket (most samplers), and INT to anything that specifically wants a plain integer instead - some third-party nodes are written that way and won't accept a SEED-typed input at all, which is exactly the friction this node exists to remove.

A practical example inside this same pack: the seed fields on Save Prompt (WLSH), Save Prompt/Info (WLSH), and Image Save with Prompt/Info File (WLSH) are all typed INT, not SEED. Originate your seed here instead of a bare native seed widget, and you can wire the SEED output to your sampler and the INT output straight to whichever of those save nodes you're logging to - one number, correctly typed for both ends, with no separate conversion node needed in between.

Installing it

ComfyUI Manager: search "wlsh_nodes" or "WLSH Nodes", install, restart. Manual: cd ComfyUI/custom_nodes && git clone https://github.com/wallish77/wlsh_nodes, then restart ComfyUI.

Common issues

There's not much to go wrong here - it's a one-job type adapter. The thing worth double-checking is that you're actually using this node's seed value as your single source of truth once you've wired it up, rather than leaving a second, separate seed widget elsewhere in your graph that's silently generating a different number. The entire point of routing through one node is to guarantee your logged seed, your sampler's seed, and any third-party node's seed all agree - if you've still got two independent seed entries in the graph, you've recreated the exact problem this node is meant to solve.