github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-16 14:39:31 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #20129] issue: Vision capability check blocks follow-up messages after Image Generation #73700

New Issue
Closed
opened 2026-05-13 06:10:03 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-05-13 06:10:03 -05:00
Owner
Copy Link

Originally created by @silentoplayz on GitHub (Dec 22, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20129

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.6.43

Ollama Version (if applicable)

N/A (I very recently swapped over to use llama.cpp server, but this should not matter)

Operating System

Ubuntu 24.04.3 LTS

Browser (if applicable)

Mozilla Firefox Snap for Ubuntu v146.0 (64-bit)

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

The model should handle follow-up messages gracefully even if an image was generated in a previous turn. Since "Vision" is disabled for the model, the system should either:

  1. Automatically exclude the previously generated image from the context sent to the model for the follow-up message.
  2. Allow the text-only follow-up to proceed without erroring on the presence of the image in history (assuming the backend or model can handle "invisible" image history or just text context). The user expects to continue the conversation after image generation without being blocked by a "not vision capable" error.

Actual Behavior

When attempting to send a follow-up message after an image has been generated in the chat, the application displays a toast notification error: "Model [Model Name] is not vision capable". This happens because the generated image is included in the conversation history, and the backend/frontend validation detects an image in the context while the model's vision capability is explicitly set to false, triggering the error catch.

Steps to Reproduce

  1. Edit a model via its edit page (Admin Settings -> Models).
  2. Toggle OFF the Vision capability for the model and save changes.
  3. Start a new chat and select this model.
  4. In the chat input integrations menu, toggle ON Image Generation.
  5. Send a query to trigger image generation (e.g., "Generate an image of a cat").
  6. Wait for the model to return the generated image.
  7. Turn OFF Image Generation (or leave it, the issue is present regardless as long as the previous image is in history).
  8. Send a text-only follow-up message (e.g., "Thanks, now tell me a joke").
  9. Observe: A notification toast appears at the top right: "Model [Name] is not vision capable", and the message is still sent to the model. The model still returns a response, either textual or with an image attached.

Logs & Screenshots

Error triggered in src/lib/components/chat/Chat.svelte:

// src/lib/components/chat/Chat.svelte around line 1740
if (hasImages && !(model.info?.meta?.capabilities?.vision ?? true)) {
    toast.error(
        $i18n.t('Model {{modelName}} is not vision capable', {
            modelName: model.name ?? model.id
        })
    );
}

The hasImages check scans the entire message history (via createMessagesList) and finds the generated image from the previous turn, causing the validation failure.

Additional Information

This error was initially reported by @Classic298, but it was requested that I open this issue.

Originally created by @silentoplayz on GitHub (Dec 22, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/20129 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!). - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.6.43 ### Ollama Version (if applicable) N/A (I very recently swapped over to use llama.cpp server, but this should not matter) ### Operating System Ubuntu 24.04.3 LTS ### Browser (if applicable) Mozilla Firefox Snap for Ubuntu v146.0 (64-bit) ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior The model should handle follow-up messages gracefully even if an image was generated in a previous turn. Since "Vision" is disabled for the model, the system should either: 1. Automatically exclude the previously generated image from the context sent to the model for the follow-up message. 3. Allow the text-only follow-up to proceed without erroring on the presence of the image in history (assuming the backend or model can handle "invisible" image history or just text context). The user expects to continue the conversation after image generation without being blocked by a "not vision capable" error. ### Actual Behavior When attempting to send a follow-up message after an image has been generated in the chat, the application displays a toast notification error: "Model [Model Name] is not vision capable". This happens because the generated image is included in the conversation history, and the backend/frontend validation detects an image in the context while the model's vision capability is explicitly set to false, triggering the error catch. ### Steps to Reproduce 1. Edit a model via its edit page (Admin Settings -> Models). 2. Toggle `OFF` the `Vision` capability for the model and save changes. 3. Start a new chat and select this model. 4. In the chat input integrations menu, toggle `ON` Image Generation. 5. Send a query to trigger image generation (e.g., "Generate an image of a cat"). 6. Wait for the model to return the generated image. 7. Turn `OFF` Image Generation (or leave it, the issue is present regardless as long as the previous image is in history). 8. Send a text-only follow-up message (e.g., "Thanks, now tell me a joke"). 9. **Observe:** A notification toast appears at the top right: "Model [Name] is not vision capable", and the message is still sent to the model. The model still returns a response, either textual or with an image attached. ### Logs & Screenshots Error triggered in `src/lib/components/chat/Chat.svelte`: ```js // src/lib/components/chat/Chat.svelte around line 1740 if (hasImages && !(model.info?.meta?.capabilities?.vision ?? true)) { toast.error( $i18n.t('Model {{modelName}} is not vision capable', { modelName: model.name ?? model.id }) ); } ``` The `hasImages` check scans the entire message history (via `createMessagesList`) and finds the generated image from the previous turn, causing the validation failure. ### Additional Information This error was initially reported by @Classic298, but it was requested that I open this issue.
GiteaMirror added the confirmed issuebug labels 2026-05-13 06:10:03 -05:00
GiteaMirror commented 2026-05-13 06:10:06 -05:00
Author
Owner
Copy Link

@owui-terminator[bot] commented on GitHub (Dec 22, 2025):

🔍 Similar Issues Found

I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions:

  1. #19825 Image Generation and Web Search trigger on every message
    by bcnation • Dec 08, 2025 • bug

  2. #20091 issue: image is regarded as binary in temp chat
    by funnycups • Dec 22, 2025 • bug

  3. #18995 issue: image generation and edition doesn’t work on temporary chats
    by futureshield • Nov 06, 2025 • bug

  4. #19864 issue:
    by Haervwe • Dec 10, 2025 • bug

  5. #19393 issue: shared chats with images - images won't show
    by Classic298 • Nov 23, 2025 • bug

Show 5 more related issues

  1. #20092 issue:
    by VideoRyan • Dec 22, 2025 • bug

  2. #19047 issue: followup questions sometimes fail to generate
    by avidwriter • Nov 08, 2025 • bug

  3. #19187 issue: Image generation menu gone.
    by calebrio02 • Nov 14, 2025 • bug

  4. #15404 issue: Image Generation Fails to Work
    by lie5860 • Jun 30, 2025 • bug

  5. #19019 issue: Image generation doesn't work with OpenRouter
    by vladkvit • Nov 07, 2025 • bug

💡 Tips:

  • If this is a duplicate, please consider closing this issue and adding any additional details to the existing one
  • If you found a solution in any of these issues, please share it here to help others

This comment was generated automatically by a bot. Please react with a 👍 if this comment was helpful, or a 👎 if it was not.

<!-- gh-comment-id:3684361108 --> @owui-terminator[bot] commented on GitHub (Dec 22, 2025): 🔍 **Similar Issues Found** I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions: 1. [#19825](https://github.com/open-webui/open-webui/issues/19825) **Image Generation and Web Search trigger on every message** *by bcnation • Dec 08, 2025 • `bug`* 2. [#20091](https://github.com/open-webui/open-webui/issues/20091) **issue: image is regarded as binary in temp chat** *by funnycups • Dec 22, 2025 • `bug`* 3. [#18995](https://github.com/open-webui/open-webui/issues/18995) **issue: image generation and edition doesn’t work on temporary chats** *by futureshield • Nov 06, 2025 • `bug`* 4. [#19864](https://github.com/open-webui/open-webui/issues/19864) **issue:** *by Haervwe • Dec 10, 2025 • `bug`* 5. [#19393](https://github.com/open-webui/open-webui/issues/19393) **issue: shared chats with images - images won't show** *by Classic298 • Nov 23, 2025 • `bug`* <details> <summary>Show 5 more related issues</summary> 6. [#20092](https://github.com/open-webui/open-webui/issues/20092) **issue:** *by VideoRyan • Dec 22, 2025 • `bug`* 7. [#19047](https://github.com/open-webui/open-webui/issues/19047) **issue: followup questions sometimes fail to generate** *by avidwriter • Nov 08, 2025 • `bug`* 8. [#19187](https://github.com/open-webui/open-webui/issues/19187) **issue: Image generation menu gone.** *by calebrio02 • Nov 14, 2025 • `bug`* 9. [#15404](https://github.com/open-webui/open-webui/issues/15404) **issue: Image Generation Fails to Work** *by lie5860 • Jun 30, 2025 • `bug`* 10. [#19019](https://github.com/open-webui/open-webui/issues/19019) **issue: Image generation doesn't work with OpenRouter** *by vladkvit • Nov 07, 2025 • `bug`* </details> --- 💡 **Tips:** - If this is a duplicate, please consider closing this issue and adding any additional details to the existing one - If you found a solution in any of these issues, please share it here to help others *This comment was generated automatically by a bot.* Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
GiteaMirror commented 2026-05-13 06:10:07 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Dec 30, 2025):

This needed some careful consideration

Since, we cannot just modify that function to check only on the user's messages for posted images.
What if the user deliberately sends an image to a model that is not vision capable, but does so, to have the image EDIT model edit the image? Even in this scenario we should not throw the error to tell the user the model isn't vision capable, because image generation is turned on.

So i think we should NOT show this error message if image generation is turned on.

That should do it.

<!-- gh-comment-id:3699199424 --> @Classic298 commented on GitHub (Dec 30, 2025): This needed some careful consideration Since, we cannot just modify that function to check only on the user's messages for posted images. What if the user deliberately sends an image to a model that is not vision capable, but does so, to have the image EDIT model edit the image? Even in this scenario we should not throw the error to tell the user the model isn't vision capable, because image generation is turned on. So i think we should NOT show this error message if image generation is turned on. That should do it.
GiteaMirror commented 2026-05-13 06:10:08 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Dec 30, 2025):

https://github.com/open-webui/open-webui/pull/20256

<!-- gh-comment-id:3699206129 --> @Classic298 commented on GitHub (Dec 30, 2025): https://github.com/open-webui/open-webui/pull/20256
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug confirmed issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#73700
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?