gemini-cli - 💡(How to fix) Fix False positive "prohibited content" on legitimate COPPA compliance code [1 participants]

Bug Description

Gemini CLI stops mid-response with "Response stopped due to prohibited content" when generating Python code that references child safety compliance terms like is_minor, is_child_account, and COPPA.

This is a false positive. The code being generated is a COPPA compliance feature designed to PROTECT children — specifically flagging minor accounts for guardian review before any data processing occurs.

Steps to Reproduce

1. Open Gemini CLI in a project directory
2. Ask Gemini to implement a function containing any of these terms:
   • is_minor
   • is_child_account
   • guardian_reviewed
   • COPPA
   • requires_guardian_review
3. Response stops mid-generation with: "Response stopped due to prohibited content"

Expected Behavior

Gemini completes the response. Child safety compliance code is legitimate software engineering — it protects children, not harms them.

Actual Behavior

Response stops at line referencing is_minor or is_child_account. The partial response is unusable.

Environment

• Gemini CLI version: (run gemini --version to check)
• OS: Kubuntu Linux 24
• Model: Gemini 3 (Auto)

Impact

Blocking legitimate child safety compliance work. Apps serving minors (COPPA-regulated) cannot use Gemini CLI to implement required age-verification and guardian consent features.

Workaround Attempted

None found. The filter appears to trigger on variable names regardless of context.

Suggested Fix

Context-aware content filtering — code implementing child protection features should not trigger the same filter as content that harms children. The intent is the opposite.