A post went up on r/StableDiffusion on Tuesday from somebody who had left a tab open overnight. They had found a ComfyUI node pack for Viggle’s Animate H3, meant to try it the next day, and when they came back the repository returned a 404. A few minutes later the author’s entire GitHub account returned a 404 as well.

We checked both this afternoon. Still gone.

We do not know why, and it is nobody’s business. People delete accounts for good reasons, and a person who gave away working code for free owes the internet nothing at all. What happened after that is the useful part.

The weights were never in danger

Viggle’s own Hugging Face organisation is fine. Viggle-Animate is sitting there with 18,815 downloads. The Qwen-Image-2.1 turbo LoRA the same team released a day earlier has 12,425. Nothing was withdrawn and nothing was gated.

What disappeared was the ComfyUI wrapper. A few hundred lines by one person that turned those weights into nodes you could drag into a graph.

So the model survived and the thing that let you run it did not, which is backwards from how most people picture this going wrong. Everybody worries about a model being pulled. Almost nobody backs up the node pack.

We counted our own

Our ComfyUI install has 25 custom node folders, 24 of them cloned from GitHub, across 21 distinct accounts.

Eighteen of those 21 are individual people. Three are organisations. That is 86 percent of the custom code in our production pipeline living in personal accounts that can be deleted by one person on one afternoon.

This is not a list of hobby extras either. The accounts include the author of ComfyUI-Manager, which is how most people install anything at all, and the author behind a large share of the video model wrappers this whole scene runs on. The most load-bearing glue in local AI video belongs to individuals, and they are doing us an enormous favour by writing it.

We checked whether any of our 24 remotes are dead today. All of them still resolve. We had never checked before, and had one of them gone quiet six months ago we would have found out the next time we rebuilt a machine.

Our own advice was half a list

Two weeks ago we wrote about what actually deserves a backup, after a reader asked what to hoard before the NVIDIA acquisition of Hugging Face closes. We gave four categories: things you cannot reproduce, the exact version you depend on, anything already living on borrowed time, and anything that took you an afternoon to find.

Every one of those examples was a model. Not one of them was code.

That was the wrong half to worry about. Big checkpoints get mirrored and reuploaded within hours of any hiccup. A 300 line node pack from a single account has no mirror and nobody whose reflex is to preserve it. It is the smallest thing in your install and the easiest to lose permanently.

Three things that take ten minutes

You already have the backup, you just cannot reinstall it. A git clone is a complete copy including history. If the pack is in your custom_nodes folder it is not lost when the remote dies. Copy that folder somewhere off the machine and you are done. The failure case is not today, it is the day you set up a new box and the install step fails.

Pin the commit, not the branch. The same argument we made about model revisions applies harder here, because node packs change faster than weights and a breaking change is much more likely than a withdrawal.

The registry keeps its own copies. Published packs on registry.comfy.org are served as zip files from ComfyUI’s own CDN rather than fetched from GitHub. We tested it rather than assuming: pulling the current rgthree-comfy version returned a 4 MB archive from cdn.comfy.org with GitHub never involved. A pack published there survives its author’s account going away. A pack installed by cloning a URL does not.

What this is not

There is a version of this story that turns into a complaint about relying on volunteers, and that version is wrong. The reason you can run a video model with generated sound on a gaming card at all is that individuals wrote the connecting code for nothing and gave it away. The answer is not to want different maintainers.

The answer is to notice which parts of your setup have exactly one copy. For most people reading this, the models are the well protected half and the code is the exposed half, and it took somebody else losing a repository at the wrong moment for us to check our own.

A daily note from our news radar. The week gets the full treatment in the DIY AI Brief every Monday.