Alignment Command (Internal)

Read the display name twice

"Alignment Command (Internal)". That's the whole story, really. This is a leftover - one of three placeholder nodes from the ComfyUI example template that HouseKeeper shipped with in its earliest versions, and it never actually worked. On current versions it doesn't exist at all: v0.7.0 deleted all three placeholders, and you won't find housekeeper-alignment-cmd anywhere in the source anymore.

The 0 clicks and 0 impressions this page gets are exactly right. There's nothing for you to use here, and no feature you're missing out on.

What its inputs tell you about a discarded design

The schema is the interesting fossil. It takes three required inputs and returns one string:

• alignment_type - an enum with the four edge directions: left, right, top, bottom
• node_ids - a JSON array serialized as a string, default "[]"
• canvas_info - a JSON object serialized as a string, default "{}"
• result - a STRING output

That shape is someone sketching a design where the panel would hand a list of node IDs plus canvas geometry to a backend "command" node and get a result string back - alignment performed server-side, through the graph. But no backend ever existed. HouseKeeper's NODE_CLASS_MAPPINGS is empty by design, and the alignment always ran client-side in the browser. So the node was unreachable from day one: registered nowhere, addable by nobody, useful to nothing.

What it means for you

Ignore it. Don't add it to a workflow, don't try to wire node_ids from a list node - you'd be driving a car that has no engine. If an old workflow you downloaded references it, just delete the node; the panel it supposedly "commanded" lives in the browser and needs nothing from the graph.

The one useful thing it explains is why HouseKeeper's alignment feels so snappy and undoes in one step. There's no graph round-trip and no execution queue involved - the panel moves node positions directly on your canvas. This command node was the discarded server-side half of that design, and it's a good reminder of how the pack actually works: everything meaningful happens in JavaScript, in your browser.

Install

It rode along with the pack, so nothing separate to install - and since v0.7.0 there's literally nothing to install at all. If you somehow still have an older HouseKeeper checkout that exposes it, update the pack and it'll disappear. Same git clone into custom_nodes as the rest of the extension, zero Python dependencies either way.