Save Positive Prompt(WLSH)

Of all the save nodes in this pack, this is the stripped-down one. No seed, no model name, no metadata bundle - it takes a positive prompt and writes it to a text file. Full stop. If the rest of the IO nodes in this pack feel like more setup than you want for a quick experiment, this is the one that asks the least of you.

What it's for. Sometimes you don't want a full prompt/seed/model record baked into an image or a structured info file - you just want a running log of "what did I actually type" as you iterate on a prompt, so you can scroll back through a plain text file later and see what worked. That's the whole use case, and the node is built to match: three fields, one output, done.

Inputs: filename (default "info"), path (default empty - writes into ComfyUI's output directory if left blank), and positive, the prompt text itself. That's it - no optional fields at all, which makes this the simplest node in the whole IO section of the pack. Outputs: none. It's a pure side-effect node (is_output_node: true under the hood) - it writes the file and that's the entire job; there's nothing to wire onward from it.

When this is the right node versus its siblings: Save Prompt (WLSH) adds negative prompt, model name, seed, and a counter - reach for that instead the moment you want more than just "what did I type." Save Prompt/Info (WLSH) goes further still, accepting the bundled INFO output from this pack's KSamplerAdvanced (WLSH) node so you're not wiring sampler settings in by hand. This node is deliberately the floor of that ladder - pick it when a positive-prompt-only log is genuinely all you're after, not as a stepping stone toward the others.

Installing it

ComfyUI Manager: search "wlsh_nodes" or "WLSH Nodes", install, restart. Manual: cd ComfyUI/custom_nodes && git clone https://github.com/wallish77/wlsh_nodes, then restart ComfyUI. No dependencies beyond the node pack itself.

Common issues

Because filename doesn't default to anything unique ("info" will just get reused every run unless you change it or add a token), the most common surprise is overwriting your own log - if you're running this repeatedly across sessions, wire something into filename that actually varies, or point different experiments at different path values so you're not silently clobbering yesterday's notes with today's. And if you're tempted to build date-stamped subfolders using a %time-style token in path: this pack's save nodes share the same underlying save logic, and the author has confirmed elsewhere in the pack that time-keyword templating isn't implemented for the path field - only for filename on the nodes that support it. Since this node's filename doesn't template at all either, the practical answer here is to compute any dynamic naming yourself with an upstream string node before it reaches filename or path.