h4 : Debug-a-Tron-3000 CONSOLE (v3.0.0) - Now in Technicolor™

The Debug-a-Tron 3000 dumps diagnostics to the console, which is great until you want to keep a run's record - attach it to a bug report, drop it in a note, or archive it next to the workflow file. That's what the Console variant is for: the full Debug-a-Tron feature set plus an html_log output that hands you the whole run as a self-contained HTML snippet.

Yes, the display name literally says "Now in Technicolor™" and the default color scheme is cyberpunk. The pack is unapologetic about its aesthetic, but underneath the neon the mechanism is sound and genuinely useful.

What's different from the base Debug-a-Tron

Everything the 3000 does - monitor/passthrough mode, all ten typed slots, GO PLUS ULTRA diagnostics - carries over. On top of that you get four output-oriented widgets:

• display_mode - console_only, html_only, or both. Default both, which is the right call for interactive debugging.
• color_scheme - dark, light, matrix, or cyberpunk. Pick light if you'll paste the report into a doc; keep cyberpunk for the full experience.
• verbosity - minimal, normal, verbose, trace. Dial it down for a summary card, up for per-tensor deep dives.
• show_timestamps - millisecond-precise stamps per section when you need to correlate events across a long run.

The outputs are html_log (STRING) plus the same ten mirrored payloads (Model, CLIP, VAE, Latent, etc.), so the Console node is output-only in spirit - it's meant to sit at the tail of a pipeline, not in the middle.

Where it fits

The classic placement is after a Debug-a-Tron 3000 or at the end of a complex graph: the HTML report appears in the output panel, you save it, embed it in a note, or pipe the html_log string into a file-write node for automated archiving. The author's framing - "HTML for stakeholder reporting, Execution Logger for the CLI loud" - is actually a decent division of labor: one for records, one for rapid iteration.

It's worth being honest about the ecosystem context: a workflow with an HTML-telemetry node is rare, and this pack has essentially zero community footprint (no search impressions, shelved by its own author). If you want a permanent, human-readable audit trail in the workflow file itself, this is one of the few nodes built around that idea. If you just need to see values fast, the plain Debug-a-Tron 3000 does the job with less ceremony.

Install

ComfyUI Manager → search "h4 ToolKit", or:

cd ComfyUI/custom_nodes
git clone https://github.com/m3rr/h4_ToolKit

Restart. Just colorama and numpy under the hood, auto-installed on startup - no models to fetch.

Troubleshooting

• No HTML appearing - check display_mode isn't set to console_only, and make sure you're reading the output panel for html_log (it's a string, so it renders as text, not a node preview).
• Report is noisy - drop verbosity to minimal; you lose tensor deep-dives but keep the summary.
• Artifacts vs. report - the JSON/preview artifacts are still gated by go_ultra and land in ComfyUI/temp/h4_debugatron_ultra/; the HTML report is independent of that and always produced.