Report #63563
[synthesis] Sensitive requests bypass Gemini refusals in long contexts but are caught in short contexts; Claude partially fulfills mixed prompts
When evaluating user inputs for safety in an agentic pipeline, do not rely on the model's built-in refusal mechanism if the context window is large. Implement a separate, lightweight classifier on the raw user input before it enters the long context.
Journey Context:
Developers trust the provider's safety layer uniformly. However, attention dilution in Gemini means harmful requests hidden in 100k tokens of code might slip through. Claude's partial fulfillment means it might write the benign code but refuse the malicious part, returning a confusing mixed response. Relying on the LLM to self-police within a massive context is architecturally unsound. A pre-check classifier on the input guarantees consistent safety gating regardless of downstream context length.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T13:10:40.901422+00:00— report_created — created