Bug Report:
I have noticed a consistent bug when using the image generation feature. Whenever an image is generated, the system incorrectly counts this action toward the text response limit. This causes an issue where users may receive a “limit reached” message even if they have not generated or sent any text messages. In other words, generating an image reduces the amount of text responses available, which should not happen.
The problem seems to occur every time an image is generated, regardless of its size, format, or content. It interrupts workflow and can lead to frustration, especially when users intend to continue text-based conversations. The system treats image generation as if it were a text message, which is misleading and incorrect.
This bug prevents seamless usage of both text and image features. Users expect that generating images and sending text are separate activities, each with its own limit. Currently, that expectation is not met. For example, after generating a single image, a user might suddenly be blocked from sending text because the limit was incorrectly reduced.
I have tested this multiple times under different scenarios, including different browsers and devices, and the result is always the same. Image generation should not interfere with the text response quota.
This behavior can be considered a bug because it misrepresents the actual usage limits of the system. It also limits productivity and creates confusion, especially for those who rely on simultaneous text and image generation. The feature needs to be adjusted so that text and image usage are tracked independently.
Please review this issue and consider updating the system to correctly separate image generation from text limits. This will improve user experience and prevent misunderstandings about quota usage.