Doom Prompt Save

Every serious prompt-hoarder hits the same wall: the image is saved, the workflow is saved, and the one prompt that actually produced the result is rattling around in your head. Doom Prompt Save is the pack's answer - a dedicated node that writes prompts to disk in three modes, with a date stamp, a reliable counter, and your choice of plain text or JSON. It's the companion to DoomSaveUltimate for people who want their prompt log separate from their image folder.

How it works

Three save modes cover the real use cases:

• single_file - append every run to one growing log file. Your "prompts of the week" journal.
• multiple_files - a fresh file per run, dated and numbered. Good for tracking individual generations.
• overwrite - clobber the file each run. Only really useful for a fixed "current prompt" reference.

You can also choose the format: txt for a human-readable log, or json which writes an entries[] array - machine-parseable, which is what you want if you're ever going to script over your history.

The inputs that matter

• prompts - the actual text to save. Multiline, so paste several prompts in one run if you like.
• output_file_path - where to put it, relative to your output/ directory. Empty means output/ itself.
• filename_prefix and filename_delimiter - the base name and the separator in the filename.
• date_in_filename - stamps each file with the date, so a "log" doesn't become an undated blob.
• save_prompts_mode - single_file / multiple_files / overwrite.
• extension - txt or json.
• metadata (optional) - arbitrary extra text that gets written into the file. Wire your seed, your model name, whatever you want attached to the prompt.

Output is a single output_message string summarizing what was saved - handy to pipe into a DoomTextShow so you get a receipt in the UI.

Setup

Standard pack install:

cd ComfyUI/custom_nodes
git clone https://github.com/PeterMikhai/Doom_Flux_NodePack

Restart ComfyUI, or find "DoomAI Nodes" in Manager. No extra dependencies - pure file I/O.

Where people get burned

• single_file grows forever. Appending is append; a month of daily runs makes a big text file. That's fine until you're scrolling 10,000 entries. Archive it periodically or switch modes.
• Paths are under output/. output_file_path is a subpath, not an absolute path. Absolute paths work too, but relative is the intended mode.
• The counter is per-prefix. Two nodes with the same prefix share the same counter file, which can surprise you if you expected separate numbering. Different prefixes, different counters.
• This node saves text, not images. It pairs with DoomSaveUltimate (which can also write its own prompt logs) - if you want the prompt bundled with the PNG metadata, the save node is the one doing that. Use DoomPromptSave when you want a standalone, searchable text archive.

For anyone who's ever rebuilt a workflow from a half-remembered prompt, this is the node that makes "what did I actually write?" a one-grep question instead of a scavenger hunt. It's from the same small, Russian-authored pack as the rest of the Doom family - unglamorous, no dependencies, does exactly one thing.