Text Prompt Combo (JPS)

This is the simplest node anywhere in the JPS pack, and there's not much to explain because it does almost nothing on purpose: two multiline text boxes, positive and negative, that pass straight through to two string outputs. No combining, no logic, no processing - just one tidy entry point for both your prompts instead of two separate text-primitive nodes scattered around your canvas.

How it works

You type into pos and neg, and the exact same text comes back out as pos and neg. That's the entire node. If you're already following JPS's settings-menu convention throughout a workflow - one node per concern, with clean, purposeful widgets - this fits the same philosophy for prompt entry: a single, visually contained place to write both prompts, rather than hunting for two different primitive text nodes and keeping them visually paired yourself.

Where it's actually useful is as the entry point feeding whatever real text processing you're doing downstream - SDXL Prompt Handling Plus (JPS) if you need G/L handling logic, a wildcard node, a translation node, or straight into your CLIPTextEncode nodes if you don't need any processing at all.

The inputs and outputs that matter

• pos (STRING, multiline, required) - your positive prompt.
• neg (STRING, multiline, required) - your negative prompt.
• Outputs: pos, neg (STRING) - identical pass-through of whatever you typed.

How to install it

ComfyUI Manager: search "JPS Custom Nodes for ComfyUI." Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/JPS-GER/ComfyUI_JPS-Nodes.git

Restart ComfyUI. No models, no dependencies - this node is about as lightweight as a custom node can be.

Common issues & troubleshooting

There's genuinely not much to troubleshoot in the node itself - it's a pass-through, so if something's not working, the bug lives downstream of it, not here. A couple of things worth checking anyway:

Your prompt "isn't working." Confirm first that this node's output is actually wired into whatever consumes it. Since there's no processing happening here, if the wire's connected correctly, whatever text you typed is exactly what's reaching downstream - useful as a quick sanity check to rule this node out before chasing a bug in your conditioning or sampler settings.

Old-version conflicts. The general JPS caveat applies here too: if you're upgrading from a previous install of the pack, delete the old copy before pulling the new one, or you risk duplicate node-class registrations across the whole pack, not just this node.

Not sure why you'd use this over a plain text node. Fair - for a simple single-prompt workflow, you probably don't need it. It earns its place mainly in more elaborate JPS-style graphs where keeping positive and negative prompt entry visually paired in one place matters, or as a clean hand-off point into a node like SDXL Prompt Handling Plus that does need both at once.