github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-17 08:21:12 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #17813] issue: Variables in model recommended prompts #18404

New Issue
Closed
opened 2026-04-20 00:37:10 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-20 00:37:10 -05:00
Owner
Copy Link

Originally created by @aleksanderson94 on GitHub (Sep 27, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17813

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Pip Install

Open WebUI Version

v0.6.31

Ollama Version (if applicable)

No response

Operating System

macOS Sequoia

Browser (if applicable)

No response

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

Clicking a recommended prompt that contains a variable opens an input field for that variable.

Actual Behavior

A recommended prompt with a variable, created in the workspace, has been added to the model. When the prompt is clicked from the recommended list, it adds the command to the chat, but the input field for the variable doesn't pop up.

Steps to Reproduce

  1. Create a prompt in the workspace that contains variables for user input.
  2. Add the command to call the prompt to the list of recommended prompts for the model.
  3. Select the chat with the model and click on the prompt.

Logs & Screenshots

Image

Image

Additional Information

No response

Originally created by @aleksanderson94 on GitHub (Sep 27, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/17813 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Pip Install ### Open WebUI Version v0.6.31 ### Ollama Version (if applicable) _No response_ ### Operating System macOS Sequoia ### Browser (if applicable) _No response_ ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior Clicking a recommended prompt that contains a variable opens an input field for that variable. ### Actual Behavior A recommended prompt with a variable, created in the workspace, has been added to the model. When the prompt is clicked from the recommended list, it adds the command to the chat, but the input field for the variable doesn't pop up. ### Steps to Reproduce 1. Create a prompt in the workspace that contains variables for user input. 2. Add the command to call the prompt to the list of recommended prompts for the model. 3. Select the chat with the model and click on the prompt. ### Logs & Screenshots ![Image](https://github.com/user-attachments/assets/69dab5b1-8cab-49e0-b3a5-6b310e8a839b) ![Image](https://github.com/user-attachments/assets/9ad02d9e-1fb7-4b76-80a0-da10ea2c41fa) ### Additional Information _No response_
GiteaMirror added the bug label 2026-04-20 00:37:10 -05:00
GiteaMirror commented 2026-04-20 00:37:11 -05:00
Author
Owner
Copy Link

@rgaricano commented on GitHub (Sep 27, 2025):

Add the variable type: My sign: {{sign | text}}
If you want it as required (can't be empty): My sign: {{sign | text:required}}

<!-- gh-comment-id:3341536948 --> @rgaricano commented on GitHub (Sep 27, 2025): Add the variable type: `My sign: {{sign | text}}` If you want it as required (can't be empty): `My sign: {{sign | text:required}}`
GiteaMirror commented 2026-04-20 00:37:11 -05:00
Author
Owner
Copy Link

@aleksanderson94 commented on GitHub (Sep 27, 2025):

Add the variable type: My sign: {{sign | text}} If you want it as required (can't be empty): My sign: {{sign | text:required}}

It works fine when the prompt is triggered by a command in the chat, but it fails when selected from the recommended list.

<!-- gh-comment-id:3341590481 --> @aleksanderson94 commented on GitHub (Sep 27, 2025): > Add the variable type: `My sign: {{sign | text}}` If you want it as required (can't be empty): `My sign: {{sign | text:required}}` It works fine when the prompt is triggered by a command in the chat, but it fails when selected from the recommended list.
GiteaMirror commented 2026-04-20 00:37:12 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Sep 27, 2025):

Intended behaviour, you should set the prompt directly to the suggestion prompts.

<!-- gh-comment-id:3342060527 --> @tjbck commented on GitHub (Sep 27, 2025): Intended behaviour, you should set the prompt directly to the suggestion prompts.
GiteaMirror commented 2026-04-20 00:37:13 -05:00
Author
Owner
Copy Link

@aleksanderson94 commented on GitHub (Sep 28, 2025):

Intended behaviour, you should set the prompt directly to the suggestion prompts.

Up to version 0.6.26, it was possible to specify just the command in the recommended prompts, rather than the entire prompt with all its variables. Now this has become inconvenient for several reasons:

  1. The need to specify the entire prompt in the recommendations for each model where it is used. If any edits are needed, they have to be made in each model individually.
  2. The input field for the recommended prompt is less convenient for entering a large amount of text than the main workspace window.

This looks like a bug related to using prompts with variables, or at the very least, a less convenient functionality than in previous versions. I kindly ask you to fix this in future updates.

<!-- gh-comment-id:3342738651 --> @aleksanderson94 commented on GitHub (Sep 28, 2025): > Intended behaviour, you should set the prompt directly to the suggestion prompts. Up to version 0.6.26, it was possible to specify just the command in the recommended prompts, rather than the entire prompt with all its variables. Now this has become inconvenient for several reasons: 1. The need to specify the entire prompt in the recommendations for each model where it is used. If any edits are needed, they have to be made in each model individually. 2. The input field for the recommended prompt is less convenient for entering a large amount of text than the main workspace window. This looks like a bug related to using prompts with variables, or at the very least, a less convenient functionality than in previous versions. I kindly ask you to fix this in future updates.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#18404
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?