Skip to main content
Prompts in Open WebUI allow you to create, manage, and share reusable prompt templates that can be invoked using slash commands in conversations. The system includes version control, access management, and collaborative features.

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., translate for /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:
  1. Type the slash command: Start typing / in the chat input to see available prompts
  2. Select your prompt: Choose from the autocomplete list or type the full command
  3. Fill variables: The UI will prompt you to fill in any template variables
  4. 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:
Restoring a version updates the prompt’s content to match that version’s snapshot. This creates a new history entry with the restored content.

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
Only the prompt creator, users with write access, and admin users can modify access permissions.

Tags and Organization

Get All Tags

Retrieve all unique tags across prompts:

Filter by Tags

Find prompts with specific tags:

Prompt Examples

Provide detailed feedback with specific suggestions.""", “tags”: [“development”, “code-quality”], “commit_message”: “Initial code review prompt” }

Best Practices

  1. Use Clear Commands: Choose short, memorable slash commands
  2. Document Variables: Use descriptive variable names in {{brackets}}
  3. Version Messages: Write clear commit messages for each update
  4. Test Before Sharing: Verify prompts work as expected before granting access
  5. Organize with Tags: Use consistent tags for easy discovery
  6. Control Access: Only share prompts with appropriate users/groups
  7. Keep Production Stable: Test changes in non-production versions first

Troubleshooting

Command Already Exists

Each command must be unique across all prompts:
Solution: Choose a different command or update the existing prompt.

Access Denied

Users need appropriate permissions to view or edit prompts:
Solution: Request access from the prompt owner or an admin.

Version Not Found

Attempting to restore or view a deleted version:
Solution: Check version history to find valid version IDs.

Next Steps

  • Learn about Functions for custom Python logic
  • Explore Skills for reusable capabilities
  • Configure Tools for extended functionality