Overview
Prompts provide:- Slash command invocation (e.g.,
/translate) - Version history and rollback capabilities
- Access control and sharing permissions
- Tag-based organization
- Metadata tracking for each version
- Search and filtering capabilities
Prompts are stored in the database with full version history. Each update creates a new version that can be activated, compared, or restored.
Creating Prompts
Through the Web Interface
1
Navigate to Workspace
Go to Workspace → Prompts in the Open WebUI interface
2
Create New Prompt
Click Create New Prompt and configure:
- Name: Display name for the prompt
- Command: Slash command (e.g.,
translatefor/translate) - Content: The actual prompt template with variables
- Tags: Optional tags for organization
3
Add Template Variables
Use double curly braces for variables in your prompt:
4
Save and Activate
Save the prompt to create the initial version. It’s automatically activated as the production version.
Via API
Create prompts programmatically:Using Prompts in Conversations
Prompts can be invoked using slash commands:- Type the slash command: Start typing
/in the chat input to see available prompts - Select your prompt: Choose from the autocomplete list or type the full command
- Fill variables: The UI will prompt you to fill in any template variables
- Send: The expanded prompt is sent to the model
Only active prompts appear in the slash command autocomplete. Use the toggle feature to enable/disable prompts.
Version Control
Every prompt update creates a new version in the history:View Version History
Retrieve all versions of a prompt:Compare Versions
Get a diff between two versions:Restore Previous Version
Set an older version as the active production version:Delete Version
Remove a version from history (cannot delete the active production version):Managing Prompts
List All Prompts
Get paginated list with search and filtering:Get Prompt by Command
Update Prompt
Updating creates a new version in the history:Update Metadata Only
Update name, command, or tags without creating a version:Metadata updates don’t create version history entries. Use this for minor changes like renaming or reorganizing.
Toggle Active Status
Enable or disable a prompt:Delete Prompt
Permanently remove a prompt and all its version history:Access Control and Sharing
Set Access Permissions
Prompts support granular access control:Permission Types
- read: View and use the prompt (slash command access)
- write: Edit the prompt, manage versions, and modify access
Access Grant Types
- user: Grant access to specific users
- group: Grant access to all members of a group
Tags and Organization
Get All Tags
Retrieve all unique tags across prompts:Filter by Tags
Find prompts with specific tags:Prompt Examples
Code Review Prompt
Code Review Prompt
Meeting Notes Summarizer
Meeting Notes Summarizer
Best Practices
- Use Clear Commands: Choose short, memorable slash commands
- Document Variables: Use descriptive variable names in
{{brackets}} - Version Messages: Write clear commit messages for each update
- Test Before Sharing: Verify prompts work as expected before granting access
- Organize with Tags: Use consistent tags for easy discovery
- Control Access: Only share prompts with appropriate users/groups
- Keep Production Stable: Test changes in non-production versions first