Teams often repeat the same chat instructions when triaging tickets, summarizing meetings, or formatting handoffs. Open WebUI prompt commands turn those repeated instructions into slash-triggered templates, so a user can insert the same structure from the chat composer without hunting through old conversations.
Prompt commands live in Workspace → Prompts. A prompt has a readable name, a command string such as support_reply, template content, optional tags, access grants, and a production version that appears in the slash menu as /support_reply.
Input variables make the command behave like a short form before the prompt reaches the composer. Mark required fields with :required and keep public commands limited to templates users should see in every slash menu, because inactive or private prompts stay out of that shared command space.
Use the command field without the leading slash when the UI shows the slash prefix separately. Short lowercase command names keep the chat menu easier to scan.
Use variables named customer_name, ticket_topic, and tone. Mark the first two variables as required and define tone as a select field with concise, friendly, and technical options.

$ curl --fail-with-body --silent --show-error "https://openwebui.example.com/api/v1/prompts/" \
-H "Authorization: Bearer <open-webui-token>"
[
{
"command": "support_reply",
"name": "Support Reply Template",
"content": "Draft a customer support reply for <customer_name> about <ticket_topic>.\n\nUse a <tone> tone and include the next action.",
"meta": {
"description": "Creates a consistent first reply for support tickets."
},
"tags": [
"support"
],
"is_active": true
}
]
Replace the site URL and token with values from the Open WebUI instance. If API access is disabled, use the prompt row and editor fields as the saved-state check.
Related: How to enable API keys in Open WebUI

