LLM Live Log (old id)

This is the node you're most likely to have loaded without ever choosing it. KinburgLLMLog is the old class id for the pack's live LLM log - the one the pack's current docs call "LLM Live Log (old id)" - superseded by the renamed Kinburg Live Log 📜. Same behavior, kept registered so graphs that were saved under the old id still load instead of erroring on a missing node. If you're reading this because an old workflow mentioned it: good news, nothing's broken, and you have a working log node.

The story is straightforward versioning. The pack renamed the node (new id KinburgLiveLog) and kept KinburgLLMLog registered as a silent alias - per the source, the old id still loads, behaves identically, and is "hidden from the picker." That last part is the tell: you can't add it fresh from the node menu anymore, you can only inherit it from an old saved graph. ComfyUI loads workflows by node id, not display name, so without this compatibility node every pre-rename workflow using the log would have failed on load with an unknown node - a classic custom-node breakage that this pack chose to paper over rather than inflict.

What it does is the live log behavior documented in its replacement: with a source node's live_preview toggle on, it streams the pack's LLM output as it generates - token counter, budget bar, tok/s, context fill, and collapsible reasoning. No inputs, no outputs, no wiring needed. The full detail lives in the Kinburg Live Log article; this node is that same behavior under an older name.

Installing

Ships in Kinburg-Nodes: ComfyUI Manager → search "Kinburg-Nodes", or:

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

It's a frontend extension backed by the pack's LLM infrastructure - you'll want llama-cpp-python (installed automatically by install.py) and a GGUF model to have anything to log.

The practical take

If you're building a new workflow, use the new id - that's what the pack expects, and it's where future fixes land. If an old workflow loads this node and works, leave it alone; upgrading it to the new id gains you nothing but a rename, and "if it's not broke, don't migrate it" is a genuinely reasonable policy in ComfyUI, where every node swap is a chance to introduce a wiring mistake.