Ino Remove File

Automated ComfyUI pipelines make a mess. Temporary images pile up in temp, processed batches linger in output, and eventually you want the workflow itself to clean up after itself. Ino Remove File is the node that deletes a file from inside the graph - using the same parent_folder / folder / filename interface as the pack's other file nodes. It's the kind of node you'll be glad exists and nervous to use, both at once.

It's part of ComfyUI Ino Nodes (nobandegani/ComfyUI-InoNodes), the 125+-node V3-schema pack, and sits in its InoFileHelper category (13 file-system nodes with a unified interface).

How it works

Inputs:

• enabled - the master kill-switch. Off means the node does nothing.
• seed - a "control after generate" input. It exists so the node re-executes (ComfyUI caches output nodes aggressively; the seed changes every run and forces the delete to actually run again).
• parent_folder - dropdown: input, output, or temp.
• folder - subfolder within that parent.
• filename - the file to remove.
• dummy_string - optional; another input whose whole purpose is to force re-execution when a value feeding the filename changes (e.g. a unique name from an upload node). Standard Ino trick.

Outputs are the pack's standard quartet: success (boolean), message (string), rel_path, and abs_path. If the file doesn't exist or can't be deleted, success comes back False with a message instead of the workflow exploding.

The reality check

There's no sugarcoating this one: it deletes files, and it's marked as an output node so it runs even if nothing consumes its outputs. Two rules of thumb that keep you out of trouble:

• The seed/dummy_string pattern exists because ComfyUI would otherwise skip the node. If your deletion "doesn't happen," check whether a value changed between runs - the node needs something to invalidate its cache.
• temp is the safe playground. Delete junk from temp and output with confidence; think twice (and test on junk first) before pointing it at input, where source images you care about live. There's no undo and no trash can. If you want a softer approach, the pack's Ino Move Path can relocate a file instead of destroying it.

When you'd use it

The realistic pattern is a pipeline tail: save a batch of images, upload the ones you keep to S3 (via the pack's S3 upload nodes), then Ino Remove File the local copies to keep disk usage flat. Chained with the pack's Ino Save Images and InoS3UploadImage, it closes the loop on fully-automated, self-cleaning batches.

Installing it

ComfyUI Ino Nodes installs like any custom node pack:

• ComfyUI Manager (easiest): search for "ComfyUI Ino Nodes", install, restart.
• Manual:

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

  Then restart ComfyUI.

Requires inopyutils and a current ComfyUI. It's a niche pack with almost no community footprint, which is honestly fine here - the fewer people pointing this node at their own input folder by accident, the better.