DP Quick Model Link

If you've got models scattered across drives, or two ComfyUI installs that both need the same checkpoints and you don't want two 6GB copies sitting around, the real fix is a symbolic link - one folder that points at another instead of duplicating the files. Most people do this from a terminal. DP Quick Model Link lets you do it from inside the graph instead, which is convenient if you're not comfortable with ln -s or mklink and don't want to leave ComfyUI to manage it.

How it works

One dropdown, three actions: create, delete, or list - and list is the default, which is a sane choice for a node that touches your filesystem. Point your_model_folder at the folder you want to become a link, and the_other_model_folder at the real location you want it to point to, then switch action to create. To remove a link you made, switch to delete and pass its path via link_to_delete. Because this is is_output_node: true, running it actually executes the filesystem operation when you queue the graph - it's not a passive preview node.

This is genuinely useful for organizing a model library across mismatched folder structures, or sharing one models directory between two separate ComfyUI installs without doubling your disk usage. It's also the kind of node where "list first" is the right habit - check what links already exist before you create or delete anything.

Inputs and outputs

Required:

• action - create, delete, or list (default list).

Optional (all default to empty string, only relevant depending on the action):

• your_model_folder - the folder that will become the symlink.
• the_other_model_folder - the real folder the link points to.
• link_to_delete - the path to remove, for the delete action.

One output: a STRING report of what happened (or, for list, what already exists).

Installing it

ComfyUI Manager: search ComfyUI-Desert-Pixel-Nodes, install, restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/DesertPixelAi/ComfyUI-Desert-Pixel-Nodes

Restart ComfyUI. No models needed for the node itself - obviously - it just touches your filesystem when you run it.

Where people get tripped up

Symlink creation needs OS-level permission, and this is the single most common wall people hit with any tool that creates symlinks, not just this one. On Windows, creating a symbolic link normally requires either running as Administrator or having Developer Mode turned on - without one of those, create will fail with a permissions error that has nothing to do with this node's own logic. On Linux/macOS it generally just works for folders you own.

Run list before you delete anything. Because this node executes real filesystem changes when queued, a mistyped path in link_to_delete either does nothing (if it doesn't match an existing link) or removes the wrong thing - always confirm the exact path with list first rather than typing from memory.

And a note on what this node does not do: it links folders, not individual files, and it doesn't move or copy anything - the original files stay exactly where they are. If you delete the link later, the real folder and its contents are untouched; only the pointer goes away.