Prompt Composability

[meissnereric]

Describe the feature or potential improvement

There are certain things I need to add to all or most of my system's prompts and we compose them just before .invoke right now (using Langchain), but would be great if I could do that in your system and get it all stored there.

For instance, we usually load in a subset of previous user conversation and that template would be helpful to add in as a component in your PromptManagement tool.

Potentially then when I load prompt C (that is composed of A + B for instance) it would automatically load both of those sub-prompts and use the config from prompt C.

Additional information

No response

[marcklingen]

Great idea, I imagine this to work like this (with some @mention UI):

Prompt A

prompt

Prompt B

prompt

Prompt C

@[Prompt A] @[PromptB]

[zoltan-fedor]

Funny, I just wanted to raise the same idea.

We have a ReAct agent, which uses multiple tools (tools are dynamically selected), so we have one prompt for the ReAct agent itself and one for each tool. At runtime we put those together (ReAct prompt + multiple tool prompts) and supply that to the LangChain ReAct agent module.

This works, but now the generations in Langfuse are not aware which prompt was used - because in fact there were multiple.

So at minimum it would be nice to have an option to tell Langfuse that this call is based on multiple prompts (which were used to compose the actual prompt).

Ps.: Although this is not exactly the same as above, as we are constructing the final prompt from the tool prompt dynamically at runtime, so the following would not be sufficient:
@[Prompt A] @[PromptB]

[marcklingen]

Now tracked independently here, thanks for sharing!

https://github.com/orgs/langfuse/discussions/4040

[jasonslyvia]

We now have a bunch of different prompts share the same system prompt, for now we just copy & paste, it would be nice to compose them.

[isc-patrick]

The current implementation is a simple template, supporting {{variable}} interpolation. Allow a template to be a variable and you are halfway there or just maybe use an existing template library? Composability is required unless everyone is OK with copy/paste and find/replace.

[marcklingen]

what makes this a bit more complicated

• server side caching that needs to be invalidated for all prompts that are related to the prompt that was updated. simple solution, invalidate all prompts of the project as reads are cheap
• render aggregated prompt and prompt variables nicely