👘 Kisekae Debug JSON

Chained nodes are lovely right up to the moment something ends up in your prompt and you have no idea which of the six nodes put it there. Six section nodes, a couple of Load Preset calls, a preset with references to three other files - that's a lot of places a huge breasts could have come from.

👘 Kisekae Debug JSON answers "why is this value here". It's a pass-through that shows the character state at the point you insert it, in three different views.

How it works

It takes char, returns char unchanged, and dumps a text view of the character into its display box. Drop it anywhere in a chain - before an Outfit node, between two section nodes, at the end - and re-queue. It's an output node, so it runs without wiring its char onward.

view picks the lens:

• resolved - clean values, the way a preset file would look. Weights only appear when they're not 1, so you're reading tags, not metadata.
• sources - every field as an object with its full bookkeeping: the value, its weight, and which node or preset supplied it. A section that came purely from a $ref also shows its origin as $ref <preset>. This is the view you want when something's overwritten and you don't know by what.
• trace - a numbered list of what each node did, in order. Not the values: the operations. It reads like load preset examples/characters/aoi (replace), then Outfit#12: section ← examples/outfits/maid, then Outfit#12: outfit.upper cleared (hidden by outfit.full = dress).

section narrows the dump to one section instead of (all). Handy when the character JSON is long enough that the node's text box makes you scroll - which it will, once a few presets are stacked.

Outputs are char (unchanged, so the chain continues) and text, the same string as the display box. The second one is genuinely useful: you can wire it into a Show Text or save node if you want the state in a log rather than a node tooltip.

The inputs and outputs

| Input | Notes | |---|---| | char | required - there's nothing to inspect without it | | view | resolved, sources, trace | | section | (all) or a single section name |

Outputs: char, text.

Install

It ships with the pack, so:

cd ComfyUI/custom_nodes
git clone https://github.com/Kagejitsu/comfyui-kisekae

Or ComfyUI Manager → search kisekae. Restart ComfyUI, and the debug nodes are under kisekae alongside the rest. No Python dependencies, no models.

Common issues

The box is empty. The node hasn't run yet. It's an output node, so queue the workflow - just connecting it isn't enough.

trace says "no operations yet". Your character arrived without any history, which usually means you're inspecting the output of a node that created a fresh character - anything with nothing connected to its optional char input starts from scratch.

The output shows more than I expected from the preset. Adding a preset and then overriding fields keeps the preset's other fields; the merge builds up rather than replaces, per field. sources will show individual fields coming from different preset files, which is correct behaviour and looks alarming the first time.

I can't see which node cleared a field. trace records clears only when there was something to remove - a (clear) on an empty field isn't logged, because nothing happened.

Output disappeared when I moved the node. It's cached like any other node; re-queue. Unlike a Prompt node, there's no IS_CHANGED fingerprint on the debug nodes, so an unchanged graph may show a stale string from the last run - that's usually fine, but re-queue if you're chasing a ghost.