RTX Remix Delete File

Sometimes a workflow's cleanup is as important as its output. RTX Remix REST API workflows generate a lot of intermediate files - temp PNGs from ingest, half-processed textures, scratch layers - and RTX Remix Delete File is the node that sweeps them up. Give it a path, it deletes the file, and it tells you whether the delete actually happened.

The interesting part is what it isn't: it's not a Toolkit API call. Under the hood it's a local Path.unlink(), pure filesystem work on the machine running ComfyUI. It still takes a context input, but only so it can sit in your graph's execution order - you can use it to say "delete the temp file after the ingest node has consumed it." So while it looks like a REST API node (it lives in the same category, prefixed 🌐), the Toolkit doesn't need to be involved in the actual deletion.

Inputs:

• path (STRING) - the file path to delete. The one field that matters.
• context - the RTXRemixContext, used for ordering, not for a request.
• enable_this_node (BOOLEAN) - the standard bypass; off means the node passes through and reports false for "deleted."

Outputs:

• context - threaded through so the rest of your graph keeps its connection info.
• File deleted (BOOL) - true if the file was removed, false if not.

That boolean is genuinely useful. If deletion is a hard requirement (say, you're clearing space before re-ingesting), you can route it into a Switch or an error check rather than just hoping the file went away. The node is careful about failure: if it can't delete the file it doesn't crash your whole graph by default, it just logs and returns false.

Install: part of NVIDIAGameWorks/ComfyUI-RTX-Remix, NVIDIA's official pack. Via ComfyUI Manager (search "RTX Remix") or:

cd ComfyUI/custom_nodes
git clone https://github.com/NVIDIAGameWorks/ComfyUI-RTX-Remix
# restart ComfyUI

Needs ComfyUI v0.3.48+ (V3 schema pack). Since it's local file deletion, you don't need the Toolkit open for the delete itself - but you do need a context to come from somewhere, so in practice it lives inside a REST API workflow that's started with RTX Remix Start Context.

Where people get burned: this is a real delete, not a recycle bin. If you point it at the wrong path, that file is gone. Keep its path fed from a source you trust (a string constant you wrote deliberately, or the output of a node you control), and use the File deleted output if you want confirmation before your workflow proceeds. Also note the context requirement - people drop this in a plain workflow expecting it to work standalone, and it can't, because the pack routes everything through context.