LTX Attn — Store Load

The mirror of Store Dump: this node loads a .pt file back into the in-memory store registry, so a capture you saved yesterday can drive today's Head Freeze, Compare Runs, or visualization nodes. It's how you turn dumped .pt archives from "backup files" into "reusable experiment data."

Its quiet superpower is the second output. Unlike every other node in this pack, Store Load returns a wireable handle output. That's a deliberate exception to the pack's usual type-the-handle-into-a-widget convention, and it's here because the store is already loaded by the time this node returns - so wiring its handle straight into downstream nodes is safe, and it saves you from retyping store names across a graph. This matters once multiple stores coexist: parallel branches, several captures in one session, that kind of chaos.

How it works

• input_path - the .pt file to load. Missing file = a clean FileNotFoundError, not a silent no-op.
• merge - false (default) replaces whatever the target handle holds with the file's contents. True merges: per-block step entries are updated into any existing store under that handle, so you can combine captures across runs into one store.
• handle - the name to load under; blank = "default". Each section present in the file goes into that name (get-or-create).

Outputs are summary (STRING, what got loaded - which blocks/steps for SA and CA, whether a QKV section was present) and the resolved handle (STRING) for wiring downstream. The handle widget in downstream nodes is a plain STRING, so this output plugs straight in.

Install

cd ComfyUI/custom_nodes
git clone https://github.com/g-raw/ComfyUI-LTX-Attention-Toolkit.git

Restart ComfyUI. No extra dependencies or model files. And the pack's standing warning applies double here: it's work-in-progress, and saved .pt files may stop loading after a version change. If a load starts erroring after an update, that's the likely cause - re-capture at the new version rather than fighting the old file.

Common issues

The load fails loudly for the two things you'd expect: a missing file, and a .pt written by an incompatible pack version. merge=True is worth a moment of thought - merging two captures with different geometries into one store can produce blocks whose steps don't align, which shows up later as weird gaps in Compare Runs or the evolution plot. When in doubt, load each capture under its own handle instead of merging.