Nodes/Kinburg-Nodes/Ouroboros Live Log πŸπŸ“œ
ComfyUI Node

Ouroboros Live Log πŸπŸ“œ

Watch the self-correcting loop correct itself

By KinburgΒ·Created 3 months agoΒ·Updated 6 days agoΒ· 1
Ouroboros Live Log πŸπŸ“œ

      Ouroboros Live Log is the display for the Ouroboros self-correcting sampler, and it is the simplest node in this pack: no inputs, no outputs, no wiring. You drop it anywhere on the canvas and it shows each iteration's thumbnail, seed, score, prompt and the critic's advice as the loop runs. That's the entire job, and it's genuinely useful - a six-iteration self-correcting run is minutes of otherwise silent GPU time, and "why did iteration 4 score worse than 3" is a question you want to answer while the loop is still going, not after.

      How it works

      There's nothing to connect because it doesn't receive data over wires at all. It's the same live-logging mechanism the pack's LLM nodes and the Morpheus/Phantas samplers use: the source node pushes events to it, and the log node renders them as timestamped blocks. Ouroboros decides how the log fills via its own log_mode input:

      • streaming - the enhancer's prompt types out token by token as it's written; the critic's verdict arrives whole (it isn't wired to the log that way).
      • per step - each stage posts the moment it finishes: enhanced prompt β†’ generated image β†’ critic verdict, each timestamped.
      • per iteration - one combined entry after the whole iteration. The older, quieter behaviour.

      So the dials that matter live on the sampler, not here. The full_console_log toggle on Ouroboros only controls terminal verbosity - the Live Log node and the report output get the full trace either way.

      When you'd bother

      Honestly, for a quick 1–2 iteration check you can skip it. Where it earns its place: a long run where you want to see the scores trend and catch a dead iteration early, or a streaming run where watching the enhancer's prompt evolve token-by-token is the fastest way to notice it's drifted off your intent. Because the block layout is different from the general Kinburg Live Log - iteration/score/stage shaped rather than generic - the pack keeps them as separate nodes; this one is specifically for the Ouroboros loop.

      Installing it

      Same pack as everything else: ComfyUI Manager β†’ search "Kinburg-Nodes", or:

      cd ComfyUI/custom_nodes
      git clone https://github.com/Kinburg/Kinburg-Nodes
      

      then restart ComfyUI. No models, no dependencies, nothing extra to download - it's pure UI. If it ever looks dead, the usual suspects are that you haven't wired the sampler's enhancer_settings/critic_settings yet (no loop, no log) or the run finished and the canvas is showing the last completed run's blocks.

      CategoryKinburg-Nodes/Bestiary/Ouroboros

      Inputs (0)

      No inputs

      Outputs (0)

      No outputs