[PR #14310] [CLOSED] feat: Implement AI-Powered Design Generation via Chat #23439

New Issue

GiteaMirror · 2026-04-20T04:49:37-05:00

GiteaMirror commented

2026-04-20 04:49:37 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/14310
Author: @Dayoooun
Created: 5/25/2025
Status: ❌ Closed

Base: main ← Head: feat/ai-design-generation

📝 Commits (1)

71fabc1 feat: Implement AI-Powered Design Generation via Chat

📊 Changes

5 files changed (+448 additions, -1 deletions)

View changed files

📝 README.md (+1 -1)
📝 backend/open_webui/utils/chat.py (+103 -0)
➕ backend/open_webui/utils/intent_processors.py (+342 -0)
📝 backend/requirements.txt (+1 -0)
➕ readme_update_draft.md (+1 -0)

📄 Description

This feature allows you to generate and iteratively refine visual designs (like posters, logos, etc.) directly through the chat interface.

Key changes include:

Backend - Intent Detection & Processing:
- I've introduced an ImageGenerationIntentDetector in backend/open_webui/utils/intent_processors.py. This function:
  - Uses keyword-based intent detection for new designs and refinements.
  - Extracts prompts from your messages.
  - Modifies previous prompts for iterative refinements.
  - Calls the existing /api/v1/images/generations endpoint using httpx.
  - Formats the response (image URL or error) as a chat message, including metadata like is_generated_design, original_prompt, and engine_used.
- I've integrated this detector into the main chat processing logic in backend/open_webui/utils/chat.py. Design generation requests are now handled by the detector, bypassing the LLM if intent is recognized.
Frontend - Image Display:
- My analysis confirmed that existing Svelte components (MarkdownInlineTokens.svelte using Image.svelte) are capable of rendering Markdown-formatted image URLs (![alt text](url)) sent by the backend.
- The Image.svelte component also provides an image preview feature.
Design Management (MVP Approach):
- For the MVP, generated images are saved via the existing file upload mechanism.
- The chat history, with messages containing image URLs and generation metadata, serves as the primary way for you to access and track their designs and refinements. No new database models for explicit design management were added.
Dependencies:
- I've added httpx>=0.25.0 to backend/requirements.txt to ensure the HTTP client for the intent detector is explicitly listed.
Documentation:
- I've drafted updates for README.md to highlight the new "AI-Powered Design Generation" feature, replacing the previous, more basic "Image Generation Integration" description.

Testing Plan:

I've prepared detailed manual end-to-end test cases, unit test cases for the ImageGenerationIntentDetector, and a frontend visual review checklist to guide developer testing.

This set of changes provides the core functionality for you to conversationally create and refine designs within Open WebUI.

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.

Before submitting, make sure you've checked the following:

Target branch: Please verify that the pull request targets the dev branch.
Description: Provide a concise description of the changes made in this pull request.
Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
Testing: Have you written and run sufficient tests to validate the changes?
Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
- BREAKING CHANGE: Significant changes that may affect compatibility
- build: Changes that affect the build system or external dependencies
- ci: Changes to our continuous integration processes or workflows
- chore: Refactor, cleanup, or other non-functional code changes
- docs: Documentation update or addition
- feat: Introduces a new feature or enhancement to the codebase
- fix: Bug fix or error correction
- i18n: Internationalization or localization changes
- perf: Performance improvement
- refactor: Code restructuring for better maintainability, readability, or scalability
- style: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
- test: Adding missing tests or correcting existing tests
- WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Description

[Concisely describe the changes made in this pull request, including any relevant motivation and impact (e.g., fixing a bug, adding a feature, or improving performance)]

Added

[List any new features, functionalities, or additions]

Changed

[List any changes, updates, refactorings, or optimizations]

Deprecated

[List any deprecated functionality or features that have been removed]

Removed

[List any removed features, files, or functionalities]

Fixed

[List any fixes, corrections, or bug fixes]

Security

[List any new or updated security-related changes, including vulnerability fixes]

Breaking Changes

BREAKING CHANGE: [List any breaking changes affecting compatibility or functionality]

Additional Information

[Insert any additional context, notes, or explanations for the changes]
- [Reference any related issues, commits, or other relevant information]

Screenshots or Videos

[Attach any relevant screenshots or videos demonstrating the changes]

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/14310 **Author:** [@Dayoooun](https://github.com/Dayoooun) **Created:** 5/25/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `feat/ai-design-generation` --- ### 📝 Commits (1) - [`71fabc1`](https://github.com/open-webui/open-webui/commit/71fabc157974895c7a6b1ecea24755506d119f1c) feat: Implement AI-Powered Design Generation via Chat ### 📊 Changes **5 files changed** (+448 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -1) 📝 `backend/open_webui/utils/chat.py` (+103 -0) ➕ `backend/open_webui/utils/intent_processors.py` (+342 -0) 📝 `backend/requirements.txt` (+1 -0) ➕ `readme_update_draft.md` (+1 -0) </details> ### 📄 Description This feature allows you to generate and iteratively refine visual designs (like posters, logos, etc.) directly through the chat interface. Key changes include: 1. **Backend - Intent Detection & Processing:** * I've introduced an `ImageGenerationIntentDetector` in `backend/open_webui/utils/intent_processors.py`. This function: * Uses keyword-based intent detection for new designs and refinements. * Extracts prompts from your messages. * Modifies previous prompts for iterative refinements. * Calls the existing `/api/v1/images/generations` endpoint using `httpx`. * Formats the response (image URL or error) as a chat message, including metadata like `is_generated_design`, `original_prompt`, and `engine_used`. * I've integrated this detector into the main chat processing logic in `backend/open_webui/utils/chat.py`. Design generation requests are now handled by the detector, bypassing the LLM if intent is recognized. 2. **Frontend - Image Display:** * My analysis confirmed that existing Svelte components (`MarkdownInlineTokens.svelte` using `Image.svelte`) are capable of rendering Markdown-formatted image URLs (`![alt text](url)`) sent by the backend. * The `Image.svelte` component also provides an image preview feature. 3. **Design Management (MVP Approach):** * For the MVP, generated images are saved via the existing file upload mechanism. * The chat history, with messages containing image URLs and generation metadata, serves as the primary way for you to access and track their designs and refinements. No new database models for explicit design management were added. 4. **Dependencies:** * I've added `httpx>=0.25.0` to `backend/requirements.txt` to ensure the HTTP client for the intent detector is explicitly listed. 5. **Documentation:** * I've drafted updates for `README.md` to highlight the new "AI-Powered Design Generation" feature, replacing the previous, more basic "Image Generation Integration" description. **Testing Plan:** * I've prepared detailed manual end-to-end test cases, unit test cases for the `ImageGenerationIntentDetector`, and a frontend visual review checklist to guide developer testing. This set of changes provides the core functionality for you to conversationally create and refine designs within Open WebUI. # Pull Request Checklist ### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) and describe your changes before submitting a pull request. **Before submitting, make sure you've checked the following:** - [ ] **Target branch:** Please verify that the pull request targets the `dev` branch. - [ ] **Description:** Provide a concise description of the changes made in this pull request. - [ ] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [ ] **Documentation:** Have you updated relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs), or other documentation sources? - [ ] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [ ] **Testing:** Have you written and run sufficient tests to validate the changes? - [ ] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [ ] **Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following: - **BREAKING CHANGE**: Significant changes that may affect compatibility - **build**: Changes that affect the build system or external dependencies - **ci**: Changes to our continuous integration processes or workflows - **chore**: Refactor, cleanup, or other non-functional code changes - **docs**: Documentation update or addition - **feat**: Introduces a new feature or enhancement to the codebase - **fix**: Bug fix or error correction - **i18n**: Internationalization or localization changes - **perf**: Performance improvement - **refactor**: Code restructuring for better maintainability, readability, or scalability - **style**: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.) - **test**: Adding missing tests or correcting existing tests - **WIP**: Work in progress, a temporary label for incomplete or ongoing work # Changelog Entry ### Description - [Concisely describe the changes made in this pull request, including any relevant motivation and impact (e.g., fixing a bug, adding a feature, or improving performance)] ### Added - [List any new features, functionalities, or additions] ### Changed - [List any changes, updates, refactorings, or optimizations] ### Deprecated - [List any deprecated functionality or features that have been removed] ### Removed - [List any removed features, files, or functionalities] ### Fixed - [List any fixes, corrections, or bug fixes] ### Security - [List any new or updated security-related changes, including vulnerability fixes] ### Breaking Changes - **BREAKING CHANGE**: [List any breaking changes affecting compatibility or functionality] --- ### Additional Information - [Insert any additional context, notes, or explanations for the changes] - [Reference any related issues, commits, or other relevant information] ### Screenshots or Videos - [Attach any relevant screenshots or videos demonstrating the changes] ### Contributor License Agreement By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-04-20 04:49:37 -05:00

GiteaMirror closed this issue

2026-04-20 04:49:37 -05:00

GiteaMirror referenced this issue

2026-04-20 06:55:45 -05:00

[PR #23439] [CLOSED] docs: Add EU AI Act compliance guide for Open WebUI deployers #27195

GiteaMirror referenced this issue

2026-04-25 14:37:09 -05:00

[PR #23439] [CLOSED] docs: Add EU AI Act compliance guide for Open WebUI deployers #42825

GiteaMirror referenced this issue

2026-04-30 02:52:30 -05:00

[PR #23439] [CLOSED] docs: Add EU AI Act compliance guide for Open WebUI deployers #50243