⭐ Star Detail Daemon

Detail Star Daemon (DetailStarDaemon) doesn't sample, doesn't upscale, and doesn't touch a single pixel after the fact. It's a settings node - it builds a detail schedule that tells a compatible StarSampler how much detail to inject during diffusion, at which point in the run, and along which curve. You connect it, the sampler does the heavy lifting. The README credits the original concept to muerrilla's sd-webui-detail-daemon (via Jonseed's ComfyUI port), and the community has a pretty clear read on what that means: it manipulates the noise during sampling to enhance details - which is why people keep mistaking it for an upscaler and getting disappointed.

What it actually changes

Five floats, one job - shaping the detail boost over the course of the run:

• detail_amount (-5 to 5, default 0.1) - strength. Positive adds detail, negative smooths. The useful band is small: 0.05–0.3 for subtle, up to ~1.0 if you want it obvious.
• detail_start (0.0–1.0, default 0.2) and detail_end (0.0–1.0, default 0.8) - the window of the sampling process where the boost applies. Boosting the whole run is usually too much; the middle of sampling is where detail is decided.
• detail_bias (default 0.5) - where the peak of the effect sits inside that window.
• detail_exponent (0–10, default 1) - how sharply the effect ramps up and down. Higher exponent = more of a spike.

Output is a single detail_schedule, which you wire into the detail_schedule input on SDstarsampler (StarSampler SD/SDXL/SD3.5) or Fluxstarsampler (StarSampler FLUX). If you're not using a StarSampler, this node does nothing for you - there's nowhere else that input plugs in.

The honest framing

This is a tuning node, and it rewards small movements. The single most common mistake is cranking detail_amount because the image "lacks detail" - but if your render is flat because the model is at its resolution limit, a daemon won't save it, it'll just make the noise look crunchy. The right mental model from the community consensus: it's for adding bite to an otherwise good render, not for rescuing a bad one. Pair it with the sampler's normal upscaling or a proper hi-res pass if you need more structure, and use the daemon for the last 10% of texture.

The defaults are conservative for a reason. Start at the defaults, bump detail_amount to 0.2, and only touch detail_start/detail_end once you can see where the run is over- or under-cooking. Negative amounts are there for the opposite case - smoothing out a noisy render without a whole denoise pass.

Install

It's part of the StarNodes pack, so the standard drill:

cd ComfyUI/custom_nodes
git clone https://github.com/Starnodes2024/ComfyUI_StarNodes

or ComfyUI Manager → search Starnodes. Restart, then find it under ⭐StarNodes/Sampler. No extra dependencies - it's pure Python with zero imports beyond the standard library, which makes it one of the most fragile-proof nodes in the pack.

When to skip it

If you're not building a workflow around the StarSamplers, skip it - its entire output contract is the DETAIL_SCHEDULE type, and only StarSamplers consume that. If you are, it's a genuinely nice addition: it's the closest thing the pack offers to a "detail slider" that works inside sampling rather than as a post-process filter, and it applies equally to Flux and the SD family.