The hint shown in the prompt editor of the workspace shows the wrong brackets.
Currently:
Format your variables using brackets like this: {{variable}}. Make sure to enclose them with {{ and }}.
Utilize {{CLIPBOARD}} variable to have them replaced with clipboard content.
The variables of prompts use angled brackets ([ and ]) instead of double curly brackets ({{ and }}).
This leads to the variables not working.
Originally created by @bannert1337 on GitHub (Jan 2, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/8268
The hint shown in the prompt editor of the workspace shows the wrong brackets.
Currently:
```
Format your variables using brackets like this: {{variable}}. Make sure to enclose them with {{ and }}.
Utilize {{CLIPBOARD}} variable to have them replaced with clipboard content.
```
The variables of prompts use angled brackets (`[` and `]`) instead of double curly brackets (`{{` and `}}`).
This leads to the variables not working.
The variables of prompts use angled brackets ([ and ]) instead of double curly brackets ({{ and }}).
This is simply untrue. Try creating a slash-command prompt with these prompt variables surrounded by double curly brackets ({{ }}) and then using it within a new chat. This works perfectly fine for me.
Note that the {{USER_LOCATION}} prompt variable requires a secure connection over HTTPS. To utilize this particular prompt variable, please ensure that Allow User Location is toggled on from the Settings -> Interface menu. The {{CLIPBOARD}} prompt variables requires access to your device's clipboard. Feel free to remove these 2 variables for testing purposes.
<!-- gh-comment-id:2567731089 -->
@silentoplayz commented on GitHub (Jan 2, 2025):
> The variables of prompts use angled brackets ([ and ]) instead of double curly brackets ({{ and }}).
This is simply untrue. Try creating a slash-command prompt with these prompt variables surrounded by double curly brackets (`{{ }}`) and then using it within a new chat. This works perfectly fine for me.
Note that the `{{USER_LOCATION}}` prompt variable requires a secure connection over HTTPS. To utilize this particular prompt variable, please ensure that `Allow User Location` is toggled on from the `Settings` -> `Interface` menu. The `{{CLIPBOARD}}` prompt variables requires access to your device's clipboard. Feel free to remove these 2 variables for testing purposes.
@silentoplayz Thanks for the clarification. I was under the impression that the variable are the fields that can be filled like a form with tabulator to move to the next.
It would be great to have all available variables and also the a hint to the form fields in the editor.
<!-- gh-comment-id:2567745560 -->
@bannert1337 commented on GitHub (Jan 2, 2025):
@silentoplayz Thanks for the clarification. I was under the impression that the variable are the fields that can be filled like a form with tabulator to move to the next.
It would be great to have all available variables and also the a hint to the form fields in the editor.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @bannert1337 on GitHub (Jan 2, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/8268
The hint shown in the prompt editor of the workspace shows the wrong brackets.
Currently:
The variables of prompts use angled brackets (
[and]) instead of double curly brackets ({{and}}).This leads to the variables not working.
@silentoplayz commented on GitHub (Jan 2, 2025):
This is simply untrue. Try creating a slash-command prompt with these prompt variables surrounded by double curly brackets (
{{ }}) and then using it within a new chat. This works perfectly fine for me.Note that the
{{USER_LOCATION}}prompt variable requires a secure connection over HTTPS. To utilize this particular prompt variable, please ensure thatAllow User Locationis toggled on from theSettings->Interfacemenu. The{{CLIPBOARD}}prompt variables requires access to your device's clipboard. Feel free to remove these 2 variables for testing purposes.@bannert1337 commented on GitHub (Jan 2, 2025):
@silentoplayz Thanks for the clarification. I was under the impression that the variable are the fields that can be filled like a form with tabulator to move to the next.
It would be great to have all available variables and also the a hint to the form fields in the editor.