MonarchAttention Status

What it is

MonarchAttention Status is a no-input node with a single STRING output: a readout of the last MonarchAttention state in your session. Fresh out of the box it reports disabled; after an Enable node runs, it shows something like enabled (model override) | impl=auto bs=128 steps=2 pad=post n=[256,4096].

That's it. It's a readout node, not a control - it doesn't change anything, it just tells you what happened.

When you'd actually use it

Honestly, as a sanity check. Attention override nodes are silent when they work. You can't tell from the output image whether MonarchAttention actually engaged or your sampler quietly ran default attention - a 2% speedup isn't visible to the eye. The Status node gives you a string to look at so you're not guessing.

Drag it onto the canvas and run once, and either read the string or wire it into a text/display node. You can see the same information in the console, but the node puts it where you can glance at it.

One caveat worth saying plainly, because it will bite you in a multi-model workflow: the status is module-global and last-write-wins. If you have MonarchAttention enabled on two model branches - a WAN high/low setup, say - this node reports whichever one applied last, not which branch is currently active. For per-branch detail you want the Enable node's verbose flag on, which records per-call timing into this same status, or the print_debug console lines ([MonarchAttention] USED / REJECT).

How it works

No mystery here. The pack keeps a module-level last_status string that the Enable and Disable nodes update whenever they run, and this node just reads it back:

• status (output, STRING) - the last MonarchAttention state: disabled, enabled (model override) | …, or disabled (model override removed).

It has no inputs and no options to set. It's not a terminal/output node in the strict sense; you just place it wherever reading a string is useful.

Install

Part of the same pack - ComfyUI Manager (search "ComfyUI_Monarch_Attention") or git clone https://github.com/xmarre/ComfyUI_Monarch_Attention into ComfyUI/custom_nodes/, then restart. No dependencies, and it works even if the vendored MonarchAttention library was never installed, because reading a status string doesn't import it.

One-sentence verdict: this is a debugging convenience, not a feature. Grab it while you're A/B testing the Enable node so you can confirm something actually engaged - then you'll forget it exists, which is fine.