Get error log

Get error log is the debugging utility hiding inside a chat pack, and it's quietly the most useful node here. ComfyUI dumps its errors into a comfyui.log file in your ComfyUI root - the place you only think to look after a workflow fails mysteriously and the console scrolled past the relevant line. This node reads that log, pulls out every line mentioning ERROR, Exception, Traceback, Failed, or Error, and hands them to you as a single STRING you can actually see in your graph. Paste it into one of this pack's chat nodes and you've got a crude but effective "here's my error, what do I do" loop - which is exactly the workflow the author demonstrates.

Mechanically it's dead simple and fully local: no inputs, no API key, no dependencies. It finds the ComfyUI root by walking up three levels from the node file, matches comfyui*.log files with a regex, picks the most recently modified one, and greps it for error lines. Output is a single STRING (the README-era version returns a Chinese "未找到错误信息。" / "no error info found" message when the log is clean - a detail that will confuse you if you're an English-only user).

Installing it

cd ComfyUI/custom_nodes
git clone https://github.com/yiwangsimple/ComfyUI_GroqChat

restart. That's it - no models, no keys, no extra pip packages. It's one of the lightest nodes in the pack.

Gotchas and honest limits

The path walk assumes a standard layout - if you run ComfyUI from a packaged/portable install where the pack isn't exactly three levels under the root, it'll report no log found. And it returns the whole matching log content as one string, so after a long session you can get a wall of text; wire it to a text display node and scroll. It also can't see errors that happen in nodes not yet executed - it reads whatever's in the log file at run time. Despite all that, for the beginner who keeps hitting node errors and has no idea where ComfyUI writes them, this node is a small revelation. It's the pack's best answer to the troubleshooting problem that the KB calls out as the number-one pain point in the custom-node ecosystem.