[GH-ISSUE #17997] feat: Variables in recommended prompts #57124

Closed
opened 2026-05-05 20:37:10 -05:00 by GiteaMirror · 11 comments
Owner

Originally created by @aleksanderson94 on GitHub (Oct 2, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17997

Check Existing Issues

  • I have searched the existing issues and discussions.

Problem Description

Discussed #17961

Desired Solution you'd like

Implement a feature that allows specifying a command (instead of static text) within the recommended prompts for a model. The expected behavior is that upon clicking a recommended prompt containing such a command, the system should properly launch the input window for the user to enter values for the variables.

Alternatives Considered

No response

Additional Context

No response

Originally created by @aleksanderson94 on GitHub (Oct 2, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/17997 ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description Discussed #17961 ### Desired Solution you'd like Implement a feature that allows specifying a command (instead of static text) within the recommended prompts for a model. The expected behavior is that upon clicking a recommended prompt containing such a command, the system should properly launch the input window for the user to enter values for the variables. ### Alternatives Considered _No response_ ### Additional Context _No response_
Author
Owner

@tjbck commented on GitHub (Oct 2, 2025):

Hmm, This should be supported today with curly bracket variables no?

<!-- gh-comment-id:3359560943 --> @tjbck commented on GitHub (Oct 2, 2025): Hmm, This should be supported today with curly bracket variables no?
Author
Owner

@aleksanderson94 commented on GitHub (Oct 2, 2025):

Hmm, This should be supported today with curly bracket variables no?

To clarify, the idea isn't to write the prompt with variables directly in the recommendations themselves. The intended workflow is to create the prompt in the Workspace, and then in the recommendations, specify only the command to call it, perhaps with some accompanying text. This used to work before (possibly unintentionally), but it has stopped working since the 0.6.27 update.

<!-- gh-comment-id:3360164908 --> @aleksanderson94 commented on GitHub (Oct 2, 2025): > Hmm, This should be supported today with curly bracket variables no? To clarify, the idea isn't to write the prompt with variables directly in the recommendations themselves. The intended workflow is to create the prompt in the Workspace, and then in the recommendations, specify only the command to call it, perhaps with some accompanying text. This used to work before (possibly unintentionally), but it has stopped working since the 0.6.27 update.
Author
Owner

@HannesStrohkopp commented on GitHub (Oct 2, 2025):

I concur with this request.

Actually, this functionality was a very important part of getting into the game the part of my users which have not too much experience with inference:
By simply selecting a use case in the suggestions below the chat bar (like e.g. "Professionalize your text...") which then auto-pasted a prepared prompt (e.g. "/professionalize_text") which then led to the actual prompt with variable field was a very low entry hurdle for them to understand prompts and how to use the UI.
Now, in this workflow, the text in the suggestion (in this example "/professionalize_text") is directly pasted and sent to the LLM without resolving the prompt template and thus the possibility to enter the variables.

It would be great if this workflow would come back to functionality!

<!-- gh-comment-id:3361190940 --> @HannesStrohkopp commented on GitHub (Oct 2, 2025): I concur with this request. Actually, this functionality was a very important part of getting into the game the part of my users which have not too much experience with inference: By simply selecting a use case in the suggestions below the chat bar (like e.g. "Professionalize your text...") which then auto-pasted a prepared prompt (e.g. "/professionalize_text") which then led to the actual prompt with variable field was a very low entry hurdle for them to understand prompts and how to use the UI. Now, in this workflow, the text in the suggestion (in this example "/professionalize_text") is directly pasted and sent to the LLM without resolving the prompt template and thus the possibility to enter the variables. It would be great if this workflow would come back to functionality!
Author
Owner

@HannesStrohkopp commented on GitHub (Oct 6, 2025):

Actually, to add on to this.

I think the easiest solution would be to remove the current auto-click when choosing a suggestion.
Then, the functionality of the aforementioned use-case would be reinstated while any other suggestions would require only one additonal click/enter.

<!-- gh-comment-id:3370520785 --> @HannesStrohkopp commented on GitHub (Oct 6, 2025): Actually, to add on to this. I think the easiest solution would be to remove the current auto-click when choosing a suggestion. Then, the functionality of the aforementioned use-case would be reinstated while any other suggestions would require only one additonal click/enter.
Author
Owner

@HannesStrohkopp commented on GitHub (Oct 28, 2025):

Kinda sad this was closed/removed.

Forces me to remove all suggestions in production. :(

<!-- gh-comment-id:3455987234 --> @HannesStrohkopp commented on GitHub (Oct 28, 2025): Kinda sad this was closed/removed. Forces me to remove all suggestions in production. :(
Author
Owner

@Classic298 commented on GitHub (Dec 14, 2025):

prompt suggestions have been refactored and can now contain variables - you only need to set it so that prompt suggestions should be inserted into the message field instead of directly sent as a message

<!-- gh-comment-id:3652221176 --> @Classic298 commented on GitHub (Dec 14, 2025): prompt suggestions have been refactored and can now contain variables - you only need to set it so that prompt suggestions should be inserted into the message field instead of directly sent as a message
Author
Owner

@HannesStrohkopp commented on GitHub (Dec 15, 2025):

Thanks for the follow-up.

Is that a setting on admin level now to insert "instead of send"?

<!-- gh-comment-id:3653998702 --> @HannesStrohkopp commented on GitHub (Dec 15, 2025): Thanks for the follow-up. Is that a setting on admin level now to insert "instead of send"?
Author
Owner

@Classic298 commented on GitHub (Dec 15, 2025):

It's in user interface settings

<!-- gh-comment-id:3654022441 --> @Classic298 commented on GitHub (Dec 15, 2025): It's in user interface settings
Author
Owner

@HannesStrohkopp commented on GitHub (Dec 15, 2025):

I see. Unfortunately, that does not really solve the issue for me. It does not help if this setting is user-specific and/or no default can be set as admin.
Most users do not go through the settings and just roll with the default config. Thus, I cannot use prompt suggestions as advertisement for preconfigured prompts. :/

<!-- gh-comment-id:3655625372 --> @HannesStrohkopp commented on GitHub (Dec 15, 2025): I see. Unfortunately, that does not really solve the issue for me. It does not help if this setting is user-specific and/or no default can be set as admin. Most users do not go through the settings and just roll with the default config. Thus, I cannot use prompt suggestions as advertisement for preconfigured prompts. :/
Author
Owner

@Classic298 commented on GitHub (Dec 15, 2025):

@HannesStrohkopp it does help because a PR is ready where admins can define the default interface settings for users and hopefully will merge soon

<!-- gh-comment-id:3655705629 --> @Classic298 commented on GitHub (Dec 15, 2025): @HannesStrohkopp it does help because a PR is ready where admins can define the default interface settings for users and hopefully will merge soon
Author
Owner

@HannesStrohkopp commented on GitHub (Dec 16, 2025):

@Classic298 Ahhh, that is perfect, thanks a ton!

<!-- gh-comment-id:3659139516 --> @HannesStrohkopp commented on GitHub (Dec 16, 2025): @Classic298 Ahhh, that is perfect, thanks a ton!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#57124