If I re-run the same ComfyUI workflow with the same seed, which parts of the code and the docs decide whether I get the same image, and what should I write down so the run can be repeated or its drift explained?
At the pinned ComfyUI commit the KSampler path draws the initial latent noise on the CPU from torch.manual_seed(seed) and casts it to the latent dtype, and the project FAQ says this is why ComfyUI seeds are 'much more reproducible' across hardware than GPU-noise UIs. That covers only the starting noise: PyTorch's own notes say bit-identical results are not guaranteed across releases, commits, platforms or CPU/GPU, ComfyUI's --deterministic is a warn-only best effort whose help text says it may not make images deterministic, and later steps (ancestral noise, dtype, attention, batch) can still differ (see -02..-04). An agent should therefore log the software, device, launch-flag and graph facts listed in the method, and describe a rerun as 'same inputs and environment' rather than guaranteed identical.
Structured fields
{
"citations": [
{
"url": "https://github.com/Comfy-Org/ComfyUI",
"note": "prepare_noise_inner; prepare_noise; FAQ"
},
{
"url": "https://github.com/comfyanonymous/ComfyUI_examples/blob/f9431bb000ce792094ff345446e22cac1ea6cef3/faq/README.md",
"note": "prepare_noise_inner; prepare_noise; FAQ"
},
{
"url": "https://github.com/pytorch/pytorch/blob/b40a4f2c025f42d1c2d4ece32daa39295b436f72/docs/source/notes/randomness.md",
"note": "prepare_noise_inner; prepare_noise; FAQ"
},
{
"url": "https://github.com/huggingface/diffusers/blob/7e4383c0a2aeb384f3d3e0003b013a40c9b1e843/docs/source/en/using-diffusers/reusing_seeds.md",
"note": "prepare_noise_inner; prepare_noise; FAQ"
}
]
}Evidence claims
- [inference] At the pinned ComfyUI commit the KSampler path draws the initial latent noise on the CPU from torch.manual_seed(seed) and casts it to the latent dtype, and the project FAQ says this is why ComfyUI seeds are 'much more reproducible' across hardware than GPU-noise UIs. That covers only the starting noise: PyTorch's own notes say bit-identical results are not guaranteed across releases, commits, platforms or CPU/GPU, ComfyUI's --deterministic is a warn-only best effort whose help text says it may not make images deterministic, and later steps (ancestral noise, dtype, attention, batch) can still differ (see -02..-04). An agent should therefore log the software, device, launch-flag and graph facts listed in the method, and describe a rerun as 'same inputs and environment' rather than guaranteed identical. · locator: prepare_noise_inner; prepare_noise; FAQ source
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| documentation | unknown | permitted | permitted | unknown | unknown | Applies to this original summary only, not to the cited sources. |
Linked records
- cites → https://github.com/comfy-org/comfyui
- cites → https://github.com/comfyanonymous/ComfyUI_examples/blob/f9431bb000ce792094ff345446e22cac1ea6cef3/faq/README.md
- cites → https://github.com/huggingface/diffusers/blob/7e4383c0a2aeb384f3d3e0003b013a40c9b1e843/docs/source/en/using-diffusers/reusing_seeds.md
- cites → https://github.com/pytorch/pytorch/blob/b40a4f2c025f42d1c2d4ece32daa39295b436f72/docs/source/notes/randomness.md