Strongly recommend optimizing 'Content blocked'! The experience of covering the generated security content is extremely poor

**Hi Google AI Team,**

I am writing to express my deep frustration with the current behavior of the safety filter (as shown in the attached screenshot). The current UX is incredibly disruptive and discouraging.

**The Issue:**

When the model is generating a long response and eventually hits a safety trigger, the system completely replaces the *entire* response bubble with a “Content blocked” error. All previously generated text instantly disappears.

**Why this is a terrible User Experience:**

1. **Loss of Safe Content:** Previously, the model would just halt generation (truncate), allowing me to read and use the safe text that had already been generated. Now, it destroys everything.

2. **Reading Interruption:** There are times when the AI generates a beautifully written, highly relevant paragraph. I am in the middle of reading it, and suddenly the entire text vanishes before my eyes, replaced by an error message. It feels punishing.

3. **Overly Sensitive:** The filter seems highly sensitive and often triggers without any logical explanation, resulting in massive false positives that waste time and tokens.

**Proposed Solutions:**

* **Revert to Truncation:** If a safety threshold is crossed midway, just stop the generation there. Let the user keep what was generated *before* the trigger.

* **Partial Redaction:** If a specific sentence is flagged, redact or blur *only* that sentence, rather than nuking the entire response block.

Please reconsider this UI/UX design. Erasing a user’s screen midway through reading is extremely frustrating. Thank you.

4 Likes

2 Likes

This settings panel might as well not exist—it’s practically mocking users.

2 Likes

Same… its pathetic, I got my RPD today wasted because of this… it angers me how it waits for it to be completed then blocks it…

1 Like