I have searched the existing issues and discussions.
Problem Description
Playground is extremely useful for simulating chat completions sent via API, since you can custom build the message call stack before calling the assistant. Substantial effort can be invested by developers creating these but the work is lost as soon as you navigate away.
Desired Solution you'd like
An additional small CRUD UI within playground to navigate previously saved playground sessions/interactions, along with an title and save button would be a minimally invasive way to achieve a pattern resembling OpenAI's current developer playground.
Alternatives Considered
Alternatively, using the the existing chat sessions, display a button or option that "adds" a user/assistant message rather than "sends" the typed message by default. That would allow developers to use the system prompt + a custom built call stack to generate API-like chatcompletion requests and leverages the existing ability to save sessions.
Disadvantages:
Developer-related sessions will mix with natural chat responses - when they don't really belong together. Non-power users maybe confused.
Additional Context
No response
Originally created by @ryanegt on GitHub (Aug 7, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16363
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
Playground is extremely useful for simulating chat completions sent via API, since you can custom build the message call stack before calling the assistant. Substantial effort can be invested by developers creating these but the work is lost as soon as you navigate away.
### Desired Solution you'd like
An additional small CRUD UI within playground to navigate previously saved playground sessions/interactions, along with an title <input> and save button would be a minimally invasive way to achieve a pattern resembling OpenAI's current developer playground.
### Alternatives Considered
Alternatively, using the the existing chat sessions, display a button or option that "adds" a user/assistant message rather than "sends" the typed message by default. That would allow developers to use the system prompt + a custom built call stack to generate API-like chatcompletion requests and leverages the existing ability to save sessions.
Disadvantages:
Developer-related sessions will mix with natural chat responses - when they don't really belong together. Non-power users maybe confused.
### Additional Context
_No response_
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 @ryanegt on GitHub (Aug 7, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16363
Check Existing Issues
Problem Description
Playground is extremely useful for simulating chat completions sent via API, since you can custom build the message call stack before calling the assistant. Substantial effort can be invested by developers creating these but the work is lost as soon as you navigate away.
Desired Solution you'd like
An additional small CRUD UI within playground to navigate previously saved playground sessions/interactions, along with an title and save button would be a minimally invasive way to achieve a pattern resembling OpenAI's current developer playground.
Alternatives Considered
Alternatively, using the the existing chat sessions, display a button or option that "adds" a user/assistant message rather than "sends" the typed message by default. That would allow developers to use the system prompt + a custom built call stack to generate API-like chatcompletion requests and leverages the existing ability to save sessions.
Disadvantages:
Developer-related sessions will mix with natural chat responses - when they don't really belong together. Non-power users maybe confused.
Additional Context
No response