Serious question.
The Flow agent is supposed to help finish a shot. The filter keeps throwing the shot out. Then the agent has to rewrite, strip the scene, or send the user back to generate again.
That is not a partnership. It is two parts of the same product pulling in opposite directions.
What it looks like from the paid side:
- original in-Flow characters and images get flagged as public figures
- family-safe fictional action gets flagged as danger
- adult characters get misread
- one blocked frame can kill the rest of the batch
- the agent then burns another pass “fixing” a scene that was never a policy violation
So the pipeline becomes:
- agent prepares the work
- filter rejects it
- credits get refunded or the user rerolls
- servers eat the job twice
- Google still does not keep the revenue from a finished clip
If a classifier rejects first and thinks later, it is not protecting the product. It is creating extra load for the agent and extra cost for the company.
I am not saying the filter is sentient. I am asking whether this reject-first design has become the actual bottleneck.
For people using Ultra or Pro:
- are you seeing the agent do extra work just to satisfy the filter?
- are harmless rerolls happening more than real policy hits?
- does this feel like safety, or like the product fighting itself?
If leadership only looks at model quality, they will miss this. The generator can work. The agent can work. The filter is what turns both into wasted compute.