Save Text With Path (CRT)

Save Text With Path (CRT) writes a string from your graph to a .txt file in a folder you choose, with a filename you control. The built-in text output nodes mostly print to the UI; this one actually persists text to the real filesystem, which is the difference between "I can see the prompt" and "the prompt is saved next to the image I rendered."

The workflow it enables: assemble your final prompt, your settings summary, or even machine-readable metadata as a string in the graph, and write it alongside the output image. Point this node at the same folder your Save Image With Path (CRT) uses and you get a tidy per-render text record - great for batch runs where you want a searchable log of exactly which prompt, seed and settings produced which image, or for feeding a prompt library that a Text Loader Crawl (CRT) can later read back from.

The inputs that matter: text (the string to write - wire it from a prompt builder, a Join Strings, or a Show Text), folder_path (absolute path of the destination folder), filename (base name, no extension, default "output"), and suffix (optional text appended to the filename). Two more worth knowing: subfolder_name lets you tuck the file into a subdirectory under the base path, and overwrite controls collision behavior. With overwrite on, an existing file gets replaced; turn it off and the node appends a numbered suffix like _001 so nothing is ever clobbered - the safe choice for long batch runs where filenames repeat.

It's an output node (no outputs), which means it sits at the end of a branch and runs when its inputs resolve. It creates directories as needed, and it's tolerant of an empty text - it writes what you give it, so if your string is blank the file will be too. There's no built-in versioning or timestamping beyond the numbered-suffix path, so if you need per-run timestamps, build them into filename or suffix upstream.

Install with the pack: ComfyUI Manager → search "CRT-Nodes", or git clone https://github.com/plugcrypt/CRT-Nodes.git into custom_nodes and restart. It's filesystem I/O - no models, no heavy dependencies. If you've been screenshotting your prompt to remember what you rendered, this is the node that replaces the screenshot with something you can actually grep.