Save String for Orchestrator

Here's the last mile of the ComfyUI Orchestration Toolkit's promise: you test a list of prompts, look at the results, and pick a winner - and the toolkit's whole point is that the winning text should flow straight back into your PromptOrchestrator for next time without you copying it out of an image and retyping it into a text box. Save String for Orchestrator is the node that closes that loop. It's the "save" in a generate → test → review → save → reuse pipeline.

It saves a text file - plain, boring, human-readable - into the PromptStorage of whichever PromptOrchestrator you're working with, so that orchestrator can load it back later from its editor. That's the whole job, and the interesting part is how much paranoia goes into doing it safely.

How it works

The node takes whatever string arrives at content - in the designed flow, that's the Chosen Prompt output of the pack's Prompt Image Picker - and writes it as a .txt file into either the CuratedPrompts or GeneratedPrompts branch of a PromptOrchestrator's storage. Files are named with your prefix and a padded counter - Prompt_00001_.txt, Prompt_00002_.txt - and it creates each file exclusively, so a save never overwrites an earlier one. Your text is preserved byte-for-byte.

The safety machinery is what you should actually know about. On every run the node walks the execution graph upstream from content looking for exactly one reachable PromptOrchestrator. Found none, or found two, and it refuses. It then checks that the folder it's about to write into really is that orchestrator's verified storage branch - path checks, symlink checks, the works - because the last thing a node like this should do is happily write files anywhere a string happens to point. That's why the content input has to originate from an orchestrator (directly or through other nodes): a hand-typed string from a plain text node has no orchestrator upstream, so it errors out. The save needs to know whose storage it's writing into.

The inputs that matter

• content - the string to save. Usually from Prompt Image Picker's Chosen Prompt.
• target_branch - CuratedPrompts (your keepers) or GeneratedPrompts (raw outputs of a generation run). Pick based on where you want the text to reappear.
• filename_prefix (default Prompt) - what the saved files start with.
• detected_prompt_orchestrator_key - don't type this yourself. A Detect Orchestrator button on the node fills it in and links the save to its orchestrator.

Output is a single filename string - the full saved path, which you can pipe into a show-text node to confirm where things landed.

Common issues

Before any of this works, the PromptOrchestrator needs its PromptStorage created: open the orchestrator's Prompt Testing → Sources and press Prompt Storage once; that builds the storage and fills the source paths. Here's the gotcha the README flags loudly: storage lives inside the installed node pack - under ComfyUI/custom_nodes/ComfyUI-Orchestration-Toolkit/PromptStorage/. Reinstall, replace, or delete that directory and your saved prompts go with it. Back the folder up if the prompts matter. If you load a workflow whose storage went missing, pressing Prompt Storage again recreates an empty one - operation is restored, but the old files genuinely can't come back.

The other errors are mostly staleness: "relationship is stale" means the orchestrator's identity changed since you pressed Detect - press it again. This node also always runs (it's marked to never be cached), because a save is a side effect that must not be skipped just because the inputs look unchanged.

Installation

Same for the whole pack - ComfyUI Manager, search "Orchestration Toolkit" (publisher flows-and-frames), or:

cd ComfyUI/custom_nodes
git clone https://github.com/flows-and-frames/ComfyUI-Orchestration-Toolkit.git

Restart ComfyUI after. No extra dependencies, no models to fetch, Python 3.10+. Like the rest of the pack this is new software (September 2026 release) with no long community track record, so lean on the README's warnings - they're unusually candid about the storage deletion risk.