Positive

Every workflow has to have somewhere for the prompt to live. In this pack, the obvious answer is the Fooocus Loader, which has a positive field built in - so why does a dedicated Positive node exist? Because graph hygiene. When you're sharing a workflow, or building one that feeds the prompt from somewhere dynamic, a visible text box labelled "Positive" is worth more than a field buried in a loader node you'd have to expand to find.

What it does

Type a prompt, get it back. It's a pure passthrough: positive (STRING, multiline) in, positive (STRING) out. No encoding, no weighting, no hidden processing - the actual prompt handling happens later, when the string gets turned into conditioning by the PreKSampler. Which means this node has exactly one job and can't surprise you.

Inputs:

• positive - the text. Multiline.

Output: positive (STRING) - wire it into the Loader's positive field, the Fooocus Expansion node's prompt input, or a standard sampler's positive prompt slot.

Installing

Part of the Seedsa/Fooocus_Nodes pack - ComfyUI Manager, search "Fooocus Nodes", or clone the repo into custom_nodes. No dependencies, no downloads. It's a text box.

The honest take

This is the pair to Fooocus negative: two plain text nodes so your prompt and your negative stay separate and obvious on the canvas. The real reason to use them is the same one behind the whole pack - workflow legibility. If you're the only person who'll ever open the graph, type into the Loader and skip both nodes. If you're sharing, or if you're building something where the prompt is generated - an Expansion node rewriting your text, a random-prompt utility, a spreadsheet of prompts - route it through here so it's unmistakable where the text enters the graph. One real note: if you type into this node and the Loader at the same time, one of them wins depending on what you wired last. Pick one source of truth and stick to it.