Check LoRAs For Updates
Find out if a creator quietly shipped a better version
- lora_stack
- lora_stack
- path
- latest_url
Civitai creators don't always announce it loudly when they push a new version of a LoRA - fix a bad epoch, retrain with better data, tighten up a likeness - they just upload a new version to the same model page. If you downloaded a LoRA six months ago and never checked back, there's a decent chance a better file is sitting there waiting and you have no way of knowing from inside ComfyUI. That's exactly the gap this node closes: point it at your LoRA stack, and it hashes every file, checks each one against Civitai, and tells you which ones have a newer version available.
How it works with the rest of the pack
This plugs into the same LoRA-stack pipeline as Sage_LoraStackLoader and Sage_ModelLoraStackLoader - build your stack with Sage's "Simple Lora Stack" / "Triple Lora Stack" nodes, and instead of (or alongside) loading it, run it through this one to get an update report. It relies on the same local cache the rest of the pack's Civitai lookups use, so if you've already loaded these LoRAs through Sage's metadata-aware nodes once, the hashes are likely already on file.
Inputs and outputs
lora_stack- required, the stack to check.force- off by default. Sage caches the "is this up to date" result so it isn't re-hitting Civitai on every single run; turning this on skips that cache and forces a fresh check. Useful right after you know a creator just shipped something, less useful as your default setting since it means an API round-trip on every execution.
Three outputs: lora_stack (the original stack, passed straight through so you can still feed it to a loader downstream), path (stringified file paths for any LoRAs that do have updates available), and latest_url (the Civitai URLs for those newer versions, so you can go download them). This node is also marked as an output node in its own right, meaning it's a valid place for a workflow to terminate - you don't have to route its outputs anywhere further if all you wanted was the check.
Installing it
ComfyUI Manager: search Sage Utils, install, restart. Or manually:
cd ComfyUI/custom_nodes
git clone https://github.com/arcum42/ComfyUI_SageUtils
cd ComfyUI_SageUtils
pip install -r requirements.txt
Restart ComfyUI. No models to download for this node specifically - it's a Civitai metadata check, not a generation step.
Common issues
This only works for LoRAs that are actually on Civitai and hash-matchable. A locally trained LoRA, a private one, or anything sourced somewhere other than Civitai has nothing to compare against, so it'll never show up as "has an update" even if you know for a fact you're running an old version - there's simply no metadata trail for the node to follow.
If you run this repeatedly and never see anything reported, don't assume it's broken - most LoRAs simply don't get updated after their initial upload, so "no updates found" is the common, correct result, not a sign of a stuck check. And if you genuinely expect an update and aren't seeing it, try force: true once before concluding something's wrong - you may just be reading a stale cached result from before the new version went live.
Inputs (2)
| Name | Type | Default | Description |
|---|---|---|---|
| lora_stack | LORA_STACK | — | |
| force | BOOLEAN | false | Force a check even if marked up to date. |
Outputs (3)
| Name | Type | Description |
|---|---|---|
| lora_stack | LORA_STACK | The original LoRA stack after update checking. |
| path | STRING | Stringified paths for any LoRAs with updates. |
| latest_url | STRING | Latest Civitai URLs for LoRAs with updates. |