gen

Run submit → poll → pick → fetch. This is the normal paid workflow. Use --budget as a hard ceiling and filters to limit scope.

pixelkiln gen --style neon --only anvil,hammer --budget 80

A mixed run requires one named ceiling for every provider it can spend through:

pixelkiln gen --budget pixellab=12 --budget retrodiffusion=0.20 --budget comfyui=0

PixelKiln validates the complete budget set before submitting the first group.

gen runs in waves. A wave is the whole lifecycle for everything the plan can act on now. Once its downloads land, assets that were blocked on a parent (a character's states, then their animations and the mirrors of those; a pro base drawn in another character's style; a revision of a still that was just made) become actionable, and the next wave takes them under what is left of the same budget, asking the same "Spend ...?" question each time unless --yes. It stops when a wave finds nothing new, when a wave submits nothing, or when the remaining budget cannot cover the next wave; in that last case the earlier waves' work is saved and the message says to run gen again with a budget for the rest. --force applies to the first wave only: a child whose parent is being regenerated waits for the parent's new bytes and then goes once, in its own wave.

After downloading a style with quality, gen points to the offline refinement step. It does not run or approve that step on the user's behalf.