Ino Move Path

ComfyUI is a file-management black hole: outputs pile up in output/, downloads land wherever the node put them, and half the time you end up ssh-ing in just to shuffle files. Ino Move Path brings that chore into the graph. It moves a file or folder from one place to another - both expressed with ComfyUI's own directory vocabulary - with an optional overwrite. The description is to the point: "Moves a file or folder from one location to another with optional overwrite."

It's part of the pack's file-helper family, which shares one design language: a parent_folder combo (input/output/temp), a folder string, and predictable success/message/rel_path/abs_path outputs so you can chain file operations together.

How it works

You give it a source (parent folder + folder + optional filename) and a destination (parent folder + folder + optional filename). It resolves both against ComfyUI's real directories - input, output, and temp map to ComfyUI's input, output, and temp folders - then moves the path. Leave from_filename empty and you're moving a whole folder; include it and you're moving a single file. overwrite (default off) controls whether an existing destination gets replaced - and moving onto an existing path without it will fail rather than silently clobber.

The inputs that matter

• from_parent_folder / to_parent_folder - the input/output/temp combos. Cross-directory moves (output → input, say, to feed a result back into a batch) work fine.
• from_folder / to_folder - the folder paths within those roots. Empty means the root itself.
• from_filename / to_filename - optional. Both empty = move the whole folder; rename in transit by setting to_filename differently.
• overwrite - off by default, and that's a good default.

Outputs: success (BOOLEAN), message, rel_path, abs_path (the destination's resolved paths, for chaining into the next file node).

Where it wires in

Automated pipelines love this. Move a finished batch from output to a dated archive folder, move a downloaded model from temp into the right subfolder, or shuffle generated assets before a zip-and-upload step (InoZip + S3 nodes complete the pattern). The success boolean also gives you a branch point for error handling.

Installing it

Part of ComfyUI-InoNodes. ComfyUI Manager → search "ComfyUI Ino Nodes" → install → restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/nobandegani/ComfyUI-InoNodes
cd comfyui_ino_nodes
pip install -r requirements.txt

Restart after. No API keys; the pack's inopyutils dependency covers the file operations.

Common issues

The usual trap is misunderstanding the destination. The node doesn't create intermediate folders for you in every case, so a to_folder that doesn't exist yet can fail - create it first with a folder operation, or make sure the path resolves. And keep overwrite in mind: it defaults off, so a move onto an existing file returns failure. That's protective, not a bug. Finally, "move" really means move - if your workflow runs twice, the source is gone on the second run, and the success=false, "Node is disabled" result you see when you toggle it off is the pack telling you it did nothing.