Process Environmental Prompt Guidence

Yes, it's spelled "Guidence" in the node's display name - that's the author's typo, not yours, and it's a fair warning that this is a small, pragmatic pack where things are labeled the way the author labels them. Process Environmental Prompt Guidence is the glue node that carries the three global prompts - scene, style, negative - through the graph while also giving you a place to actually see them.

Here's the thing about Pseudocomfy's snapshot workflow: your prompts arrive as data, not as text widgets. The scene prompt, style prompt, and negative all come out of PseudoUnpackModelSnapshot as wires, and there's no obvious place to glance at them before they hit the conditioning nodes. This node is that place. It takes env_scene, env_style, env_negative in, returns all three back out untouched (deep-copied), and adds a fourth output, env_all, which is the three joined with "; " in one string.

What it's really for

• Pass-through with a label. Wire it between the unpacker and your Apply nodes and you get a named, visible stop in the graph where the global prompts are inspectable. When a render's mood is wrong, the first thing you want is to see what the scene prompt actually said - this is where you look.
• A combined prompt for preview. env_all gives you the full global instruction as one string, which you can feed to a PseudoPreviewStrings or any text display node.
• UI metadata. It writes the three prompts back into the workflow's saved node data when it runs, so they survive in the PNG's embedded workflow. Open the image later and the scene/style/negative you used are right there in the graph.

Because it's an output node (OUTPUT_NODE = True), ComfyUI treats it as a terminal - you can run the graph up to it and stop, which makes it genuinely handy as a "checkpoint" while you're iterating on prompts before committing to a full render.

The honest take

Functionally it does nothing to its inputs - if all you need is a pass-through, a reroute node would do. What you're paying for is the preview surface and the metadata side effect, and in a data-driven workflow that's worth a node. It also quietly enforces the pack's "; " convention: env_all joins with semicolons, matching how the Apply nodes compose scene and style before encoding.

No weights, no install beyond the pack itself (git clone https://github.com/Pseudotools/Pseudocomfy into custom_nodes, or Manager → "Pseudocomfy"). If your graph feels like a black box between snapshot and sampler, drop this node in the middle and it gets a lot more legible.