Nodes/XB_ToolBox/XB-BOX - Dashboard Zen
ComfyUI Node

XB-BOX - Dashboard Zen

A clean control panel for your messy workflow, without rebuilding it

By wjluoxiao·Created 5 months ago·Updated 6 days ago· 302
XB-BOX - Dashboard Zen

      XB Dashboard Zen is the answer to a very specific kind of ComfyUI pain: you've built a big workflow, it works, and now every time you want to tweak the seed or the denoise you have to go spelunking through twenty nodes to find the one control you actually touch. This node gives you a fixed, clean "dashboard" that mirrors the controls from your real nodes, so you adjust everything from one place - without re-architecting the graph.

      The author's framing calls it a "Mirror Clone Console," and that's exactly right. It's not a new set of parameters; it's a front-end over the parameters you already have.

      How it works

      Here's the thing that surprises people: the Python side of this node is a deliberate no-op. It has no inputs, no outputs, and its function is literally "do nothing." All the real work lives in the pack's JavaScript (js/xb_dashboard.js), which hooks into ComfyUI's graph at the UI level.

      In the UI you designate a "mother node" - the real node whose widgets you want mirrored. The dashboard creates a clone that displays those widgets and syncs them two ways: change the seed on the dashboard and the mother node updates; change it on the mother node and the dashboard follows. The sync runs on an interval, so it catches live changes, and it even copies image previews over. If the mother node gets deleted or disconnected, the dashboard entry turns red with a "⚠️ Mother Node Disconnected" banner instead of silently going stale - which is more honest than most mirror tools in this space.

      Because it's a LiteGraph/UI layer trick, the dashboard doesn't change your execution graph at all. The actual compute still happens in the mother nodes; the dashboard is a mirror, not a replacement.

      When to use it (and when not to)

      Use it when a workflow is done and you're in tuning mode - the classic case is handing a template to someone (or your future self) and wanting them to only touch the controls that matter. It shines for demoing, for sharing, for "I just want the sliders."

      Don't use it as a crutch for a workflow that's still under construction. The mirror adds UI complexity, and if you're still moving nodes around, you'll spend time resyncing mirrors you were about to delete anyway. And because the sync is interval-based, rapid-fire changes on the dashboard can momentarily lag the mother node - fine for parameter tweaks, wrong tool if you need strict instant consistency.

      Install

      Standard XB_ToolBox install: ComfyUI Manager → search XB_ToolBox, or:

      cd ComfyUI/custom_nodes && git clone https://github.com/wjluoxiao/XB_ToolBox.git
      

      then restart ComfyUI. Because it's a JS feature, a stale browser tab after an update is the one real gotcha - hard-refresh (Ctrl+Shift+R) if the dashboard panel behaves oddly after the pack updates. There's also a startup cleanup in the code that removes a corrupted dashboard group if one lingers from a crash, so a weird leftover "🎮 XB Dashboard Zen" group is usually self-healing.

      CategoryXB_ToolBox/Dashboard

      Inputs (0)

      No inputs

      Outputs (0)

      No outputs