✏️ Literal String

The plainest way to get a block of text into a graph as its own node: type or paste whatever you want into Literal String, and it comes out the other side as a STRING output you can wire to as many downstream nodes as you like. No prompt weighting, no wildcard resolution, no template logic - just the text you gave it.

How it works

It's a constant, same idea as this pack's Literal Bool/Literal Float siblings but for text, and it supports multiple lines. Whatever you type in value is exactly what comes out - nothing gets parsed, evaluated, or transformed along the way. It exists for the same reason as those siblings: ComfyUI lets you "convert to input" on most text widgets, and once a value is a socket instead of a box baked into one node, something has to sit on the other end and hold it.

The inputs and outputs that matter

• value - a multiline string field, default empty. That's the whole node.
• Output: value (STRING), unchanged.

How to install it

Via ComfyUI Manager: search ComfyUI-mnemic-nodes, install, restart. Or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/MNeMoNiCuZ/ComfyUI-mnemic-nodes

Restart ComfyUI afterward. No dependencies, no model files - pure text storage.

Common issues & troubleshooting

Where this earns its place over just typing text into a CLIPTextEncode widget directly: when the same piece of text needs to feed more than one place at once. A filename template, a style block you're reusing across a positive prompt and a Save Image With Metadata filename token, a fixed system instruction you're feeding into a Groq LLM node - anything you'd otherwise have to copy-paste and keep in sync manually is a good candidate for one shared Literal String.

The thing to remember is that it really is just a literal - there's no wildcard resolution happening here (that's the pack's separate Wildcard Processor node, which reads from wildcard files and inline lists), and no string manipulation. If you need to split, extract, or concatenate text, this pack also ships dedicated nodes for that (String Concat / Append, String Text Splitter, String Text Extractor) - Literal String is just the starting point that holds a fixed value, not the tool that transforms one.

There's also nothing stopping you from using several of them side by side and letting String Concat / Append do the joining - a Literal String for a fixed style suffix, another for a negative-prompt boilerplate block, both feeding into one final assembled prompt. Keeping each piece as its own node makes a long prompt easier to edit than one giant text box, since you can see and adjust each component without hunting through a wall of text for the one line you meant to change.