[GH-ISSUE #23713] feat: Refine Prompt Variables UI to include instructions and custom labels #58717

New Issue

GiteaMirror · 2026-05-05T23:46:05-05:00

GiteaMirror commented

2026-05-05 23:46:05 -05:00

Originally created by @mrkrsl on GitHub (Apr 14, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23713

Check Existing Issues

I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.

Verify Feature Scope

I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.

Problem Description

The current set-up for Prompt Variables is promising, but it lacks refinements to be useful.

I can render a form in the UI on invoking a /prompt where a variable is defined like this:

{{client_name | text:placeholder="e.g. Acme Payments Ltd":required}}

This renders with the variable name client_name as the form label with no additional context other than the placeholder text inside the rendered field.

Desired Solution you'd like

This request is to moderately extend the feature so that:

A human readable label can be defined as the field label displayed to the user.
Additional surrounding text (e.g. explanatory text and headings) can be displayed to the user in the form.

e.g. a prettier/human readable label canbe defined like this:

{{client_name | text:label="Client Name":placeholder="e.g. Acme Payments Ltd":required}}

also, additional text can be defined surrounding the form field(s):

## Basic details
Please supply basic company information.
{{client_name | text:label="Client Name":placeholder="e.g. Acme Payments Ltd":required}}
{{client_role | text:label="Client Role":select:options=["Customer","Supplier"]:required}}

Alternatives Considered

Hacking the variable names so they're more meaningful for users. However, client_requires_license_rights is still ugly and can't include punctuation.

Additional Context

No response

Originally created by @mrkrsl on GitHub (Apr 14, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/23713 ### Check Existing Issues - [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request. ### Verify Feature Scope - [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions. ### Problem Description The current set-up for Prompt Variables is promising, but it lacks refinements to be useful. I can render a form in the UI on invoking a /prompt where a variable is defined like this: `{{client_name | text:placeholder="e.g. Acme Payments Ltd":required}}` This renders with the variable name `client_name` as the form label with no additional context other than the `placeholder` text inside the rendered field. ### Desired Solution you'd like This request is to moderately extend the feature so that: 1. A human readable label can be defined as the field label displayed to the user. 2. Additional surrounding text (e.g. explanatory text and headings) can be displayed to the user in the form. e.g. a prettier/human readable label canbe defined like this: `{{client_name | text:label="Client Name":placeholder="e.g. Acme Payments Ltd":required}}` also, additional text can be defined surrounding the form field(s): ``` ## Basic details Please supply basic company information. {{client_name | text:label="Client Name":placeholder="e.g. Acme Payments Ltd":required}} {{client_role | text:label="Client Role":select:options=["Customer","Supplier"]:required}} ``` ### Alternatives Considered Hacking the variable names so they're more meaningful for users. However, `client_requires_license_rights` is still ugly and can't include punctuation. ### Additional Context _No response_

GiteaMirror closed this issue

2026-05-05 23:46:09 -05:00

GiteaMirror commented

2026-05-05 23:46:12 -05:00

@Classic298 commented on GitHub (Apr 14, 2026):

could also be done using rich UI in tools and actions and execute() events if Rich UI is not the solution you are looking for here.

The prompt variables originally were meant to be quickly pastable highlighted areas you could navgiate with tab quickly - and later those variables were put in a form.

If you want more customization it might make sense to look into rich UI and actions and tools and execute event calls

Needs discussing

@Classic298 commented on GitHub (Apr 14, 2026): could also be done using rich UI in tools and actions and execute() events if Rich UI is not the solution you are looking for here. The prompt variables originally were meant to be quickly pastable highlighted areas you could navgiate with tab quickly - and later those variables were put in a form. If you want more customization it might make sense to look into rich UI and actions and tools and execute event calls Needs discussing

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#58717