[GH-ISSUE #20635] feat: Image Generation text does not match prompt passed to image generator #106237

New Issue

GiteaMirror · 2026-05-18T04:29:34-05:00

GiteaMirror commented

2026-05-18 04:29:34 -05:00

Originally created by @hightide82 on GitHub (Jan 13, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20635

Check Existing Issues

I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.

Verify Feature Scope

I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.

Problem Description

Hi! I installed the third-party function to restore the old image generation button functionality as the integrated tool method does two things that are undesirable:

Generated text does not correspond to prompt passed to the image generator (presumably because it generates it twice)
Cannot edit text directly and resubmit to the image generator.

These two reasons made the image generation button quite useful. Unfortunately the new function does not use the global JSON workflow and appears to override it. So I am going to roll back my install to 0.6.43 for now.

I understand UX reasons for wanting to kill the button and just wanted to share my experience. Thank you for reading, for your excellent software, and I wish you great success in your endeavors.

Desired Solution you'd like

The text displayed after generating an image should be the text that was passed to the image generator.

Alternatives Considered

No response

Additional Context

No response

Originally created by @hightide82 on GitHub (Jan 13, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/20635 ### Check Existing Issues - [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request. ### Verify Feature Scope - [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions. ### Problem Description Hi! I installed the third-party function to restore the old image generation button functionality as the integrated tool method does two things that are undesirable: 1. Generated text does not correspond to prompt passed to the image generator (presumably because it generates it twice) 2. Cannot edit text directly and resubmit to the image generator. These two reasons made the image generation button quite useful. Unfortunately the new function does not use the global JSON workflow and appears to override it. So I am going to roll back my install to 0.6.43 for now. I understand UX reasons for wanting to kill the button and just wanted to share my experience. Thank you for reading, for your excellent software, and I wish you great success in your endeavors. ### Desired Solution you'd like The text displayed after generating an image should be the text that was passed to the image generator. ### Alternatives Considered _No response_ ### Additional Context _No response_

GiteaMirror closed this issue

2026-05-18 04:29:34 -05:00

GiteaMirror commented

2026-05-18 04:29:36 -05:00

@silentoplayz commented on GitHub (Jan 13, 2026):

Regarding the double-generation issue:
You're absolutely right that the integrated tool can sometimes result in duplicated or mismatched text. This happens because the LLM generates both the image prompt AND a response about the image, which can lead to inconsistencies.

A note on the global JSON workflow:
The third-party Generate Image Action deliberately operates outside the global workflow to provide the specific behavior you need. This is by design. I treat that as a feature, not a bug. Third-party functions should offer alternatives when the built-in tools don't meet every user's needs. There's nothing wrong with using the function if it works better for your workflow.

The Advantage: User-Level Flexibility

Capability	Benefit
Configure before execution	Size, steps, sampler, etc. can be tuned in the chat-controls sidebar — no admin ticket required.
User autonomy	Experiment freely without waiting for a global policy change.

The Global-Workflow Trade-off

Integrated tool behaviour	Consequence
Locked to global defaults	Users can’t override without admin rights.
Shared configuration	One size fits all; every user inherits the same values.
Instance-wide impact	Any change ripples across every account.

@silentoplayz commented on GitHub (Jan 13, 2026): **Regarding the double-generation issue:** You're absolutely right that the integrated tool can sometimes result in duplicated or mismatched text. This happens because the LLM generates both the image prompt AND a response about the image, which can lead to inconsistencies. **A note on the global JSON workflow:** The third-party [Generate Image Action](https://openwebui.com/posts/3fadc3ca-c955-4c9e-9582-7438f0911b62) deliberately operates outside the global workflow to provide the specific behavior you need. This is by design. I treat that as a feature, not a bug. Third-party functions should offer alternatives when the built-in tools don't meet every user's needs. There's nothing wrong with using the function if it works better for your workflow. --- ### The Advantage: User-Level Flexibility | Capability | Benefit | |-----------|---------| | Configure before execution | Size, steps, sampler, etc. can be tuned in the chat-controls sidebar — no admin ticket required. | | User autonomy | Experiment freely without waiting for a global policy change. | --- ### The Global-Workflow Trade-off | Integrated tool behaviour | Consequence | |--------------------------|-------------| | Locked to global defaults | Users can’t override without admin rights. | | Shared configuration | One size fits all; every user inherits the same values. | | Instance-wide impact | Any change ripples across every account. |

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#106237