Feature Request

[curiosity2203]

Add optional STRING input socket to PromptManagerText node

The feature request is related to a problem? See description.
Currently, the PromptManagerText node only accepts text via its internal widget. It does not have an external STRING input socket. This makes it difficult to integrate with dynamic prompt generation nodes (like Searge LLM, LLM nodes, or randomizers) because we cannot pass generated text directly into PromptManager for saving/logging without using workarounds like bypass nodes or API calls.

The solution I would like
Add an optional STRING input socket to the PromptManagerText node.

• If connected: Use the text from the input socket.
• If disconnected: Fall back to the internal widget text (preserving current behavior).

Alternatives I have considered

• Using the standard PromptManager node (but it requires CLIP input and outputs CONDITIONING, which isn't always desired).
• Using the API side-channel (works, but adds extra nodes to the workflow).
• Using Fast Bypasser nodes to toggle between manual and generated text (clunky).

Additional context
This would greatly improve workflows involving LLM prompt generation, allowing users to automatically log AI-generated prompts to the database while still passing the text downstream to CLIPTextEncode or concatenation nodes.

Workflow example:
[Searge LLM] → [PromptManagerText (input)] → [Text Concatenate] → [CLIPTextEncode]

[vitosans]

Hello,

wouldn't this work?

[vitosans]